Community
Participate
Working Groups
I've created a specialized column loader for SQL Server which will set a IdentitySpecifier on a column which has IDENTITY flavor.
Created attachment 82383 [details] Patch for org.eclipse.datatools.enablement.msft.sqlserver (for HEAD) Introduces an extension for creating the specialised ColumnLoader for SQL Server. I understand this (declarative) way to be the new/preferred way of specialising the schema, as opposed to specializing the domain objects themselves. If I'm mistaken, I'll gladly do it the other way around. This patch also adds jTDS compatibility for SQL Server 2000, see the second patch in bug 208776.
Created attachment 82386 [details] Patch for org.eclipse.datatools.enablement.msft.sqlserver.profile (against 1.5.1) For those who want to test this against the released version, this is for you.
Created attachment 82387 [details] Binary patched bundle for instant testing This bundle for 1.5.1 is patched, with a bumped version qualifier number. Drop it into eclipse/plugins and restart Eclipse. To test it, create a table with an IDENTITY column (in SQL Server!) and then try to insert a row in the data table editor. This will fail before this patch, but succeed with it.
(In reply to comment #3) > To test it, create a table with an IDENTITY column (in SQL Server!) and then > try to insert a row in the data table editor. This will fail before this patch, > but succeed with it. By the way, to test this, you will likely run into bug 207331, so apply the patch for that one before you try this one. I realize that the current patch doesn't capture all information which may be stored in the IdentitySpecifier object, and the information at present can't be regenerated into DDL, but it makes the data table editor a lot more useful. Any comments or review of the patch would be appreciated.
Delivered to 1.6 head stream for SQL Server profile
Closing bugs
