Comments
Sort by recent activity
Just sent it to support email. / comments
Just sent it to support email.
Screenshot of what? / comments
Screenshot of what?
I checked version and it's the same: 11.2.0.3.0
I tried comparing it myself with all_tab_cols and found this:
CHAR_USED - production has B, local C. DATA_LENGTH - production has 1, local 4.
PL/SQL developer shows VARCHAR2(1) in both cases. Can this be caused by server configuration? / comments
I checked version and it's the same: 11.2.0.3.0
I tried comparing it myself with all_tab_cols and found this:
CHAR_USED - production has B, local C. DATA_LENGTH - production has 1, local 4.
PL/SQL ...
So can we have an option to ignore CHAR_USED ? / comments
So can we have an option to ignore CHAR_USED ?
What details do you need apart from table schema definition? / comments
What details do you need apart from table schema definition?
News fro jetbrains: http://blogs.jetbrains.com/dotnet/2011/02/resharper-6-bundles-decompiler-free-standalone-tool-to-follow/ / comments
News fro jetbrains: http://blogs.jetbrains.com/dotnet/2011/02/resharper-6-bundles-decompiler-free-standalone-tool-to-follow/
So far, your only response to this has been, "Lutz done it! It's not our fault! Buy v7 and it won't ever expire, honest guv!" You have completely ignored the huge difference between forcing users of a free program to upgrade to the latest free version, and forcing users of a free program to upgrade to a paid-for version. What you are doing here can only be compared to extortion.
I completely agree. The fact that Lutz put the time bomb does not mean that you can't or shouldn't remove it when you releasing a new paid version. You just do not want to remove it and are blaming Lutz for it. He was not selling the product but you changed that. Why don't you make another change and remove the time bomb?
Anyway, a new decompiler is being developed by Mono.Cecil author so I believe it will be enough for developers so that they will not have to by it from you. / comments
So far, your only response to this has been, "Lutz done it! It's not our fault! Buy v7 and it won't ever expire, honest guv!" You have completely ignored the huge difference between forcing use...
In my opinion redgate should at least remove the time bomb from current version. They should also release source code so that it can be maintained by the community.
Otherwise it will be just a matter of time before a cracked version or patch is released. / comments
In my opinion redgate should at least remove the time bomb from current version. They should also release source code so that it can be maintained by the community.
Otherwise it will be just a matt...
It would be nice if the static data support is added to the product. Also, it would be nice if it was possible to choose which part of the static data should go under source control.
For example,
Data that comes with default installation of my program should be source controled but the data that developer inserts through the program to check his work should not. Basically, if the data is inserted/updated/deleted from ssms then it should be in source control otherwise it should not. It would be nice if you included similar feature in the program. / comments
It would be nice if the static data support is added to the product. Also, it would be nice if it was possible to choose which part of the static data should go under source control.
For example,
D...
I guess I didn't explain it well.
There is two kinds of static data in the database:
1. The static part of the data that comes with the installation and cannot be edited/added/deleted by the user. This should be in source control. If the developer makes changes to the data with ssms it should be reflected in source control. It can be solved with sql data compare as it is possible to limit what to synchronize
2. Preconfigured values that can be changed. For example default data for a dropdownbox. The user can add/edit/delete data from the program.
This should be in source control. However when a developer modifies some data to it through the program it shouldn't go in source control. A possible solution can be to have a isdefault column which distinguishes between default and user data. The problem with this approach is that if preconfigured record is modified or deleted from the program (so isdefault is true) it should not be changed in the source control.
Thanks. / comments
I guess I didn't explain it well.
There is two kinds of static data in the database:
1. The static part of the data that comes with the installation and cannot be edited/added/deleted by the user. ...