Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Dali » DDL generation and dbdefinition xmi
DDL generation and dbdefinition xmi [message #434022] Sun, 17 September 2006 17:06 Go to next message
Tzanko is currently offline Tzanko
Messages: 2
Registered: July 2009
Junior Member
Hi,

The issue is related to the defaultPrecision, defaultScale, defaultLength
attributes of the predefinedDataTypeDefinitions element in the
DatabaseVendorDefinition XMI file.

It seems that none of these default values is considered during DDL
generation. All I could see during debugging is that the DDL generation
always uses the default values from ColumnImpl.

This is quite a major issue: for example there is no way to map BigDecimal
to something like NUMERIC(12,2) (it will always come as NUMERIC(0,0)).

Am I missing something? Any comments, ideas will be extremely appreciated.

Best Regards,

Tzanko
Re: DDL generation and dbdefinition xmi [message #434029 is a reply to message #434022] Tue, 19 September 2006 16:36 Go to previous message
Neil Hauge is currently offline Neil Hauge
Messages: 469
Registered: July 2009
Senior Member
This appears to be a limitation of our DDL Generation functionality. This
code was contributed to the project and is no longer being maintained. As
a result of this, and given that all of the JPA runtime implementations
already implement DDL generation from Entities, we have decided to remove
our DDL generation support and instead integrate with the JPA runtime
support from the Dali UI.

Due to this change in direction, we don't plan on enhancing the current
DDL generation code now or in the future unless someone is able to commit
to maintaining this functionality.

You may want to try using the DDL generation available in the JPA runtimes
to get around this issue, or use a DB tool to modify your column
definitions as appropriate after table generation from Dali.

Neil

Tzanko Stefanov wrote:

> Hi,

> The issue is related to the defaultPrecision, defaultScale, defaultLength
> attributes of the predefinedDataTypeDefinitions element in the
> DatabaseVendorDefinition XMI file.

> It seems that none of these default values is considered during DDL
> generation. All I could see during debugging is that the DDL generation
> always uses the default values from ColumnImpl.

> This is quite a major issue: for example there is no way to map BigDecimal
> to something like NUMERIC(12,2) (it will always come as NUMERIC(0,0)).

> Am I missing something? Any comments, ideas will be extremely appreciated.

> Best Regards,

> Tzanko
Re: DDL generation and dbdefinition xmi [message #589230 is a reply to message #434022] Tue, 19 September 2006 16:36 Go to previous message
Neil Hauge is currently offline Neil Hauge
Messages: 469
Registered: July 2009
Senior Member
This appears to be a limitation of our DDL Generation functionality. This
code was contributed to the project and is no longer being maintained. As
a result of this, and given that all of the JPA runtime implementations
already implement DDL generation from Entities, we have decided to remove
our DDL generation support and instead integrate with the JPA runtime
support from the Dali UI.

Due to this change in direction, we don't plan on enhancing the current
DDL generation code now or in the future unless someone is able to commit
to maintaining this functionality.

You may want to try using the DDL generation available in the JPA runtimes
to get around this issue, or use a DB tool to modify your column
definitions as appropriate after table generation from Dali.

Neil

Tzanko Stefanov wrote:

> Hi,

> The issue is related to the defaultPrecision, defaultScale, defaultLength
> attributes of the predefinedDataTypeDefinitions element in the
> DatabaseVendorDefinition XMI file.

> It seems that none of these default values is considered during DDL
> generation. All I could see during debugging is that the DDL generation
> always uses the default values from ColumnImpl.

> This is quite a major issue: for example there is no way to map BigDecimal
> to something like NUMERIC(12,2) (it will always come as NUMERIC(0,0)).

> Am I missing something? Any comments, ideas will be extremely appreciated.

> Best Regards,

> Tzanko
Previous Topic:Error when the project was closed
Next Topic:Interopearbility with EMF Model
Goto Forum:
  


Current Time: Mon Sep 22 20:33:38 GMT 2014

Powered by FUDForum. Page generated in 0.01661 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software