Re: [Wonder-disc] ERMigration: generate foreign key constraint broken?

[Marius S. <m.s...@st...>]

You can define a shorter name for each of your FK constraints with a property like this:

er.extensions.ERXModelGroup.ERXMigrationTable_ENTITY_NAME.ORIGINAL_FK_NAME.foreignKey=YOUR_SHORT_NAME

Should be documented somewhere :)


On 30.11.2010, at 14:11, René Bock wrote:

> Hi,
> 
> After migrating to the current Wonder5.4 frameworks, i suddenly get the following exception:
> 
> MySQLSyntaxErrorException: Identifier name 'PanelResendTransactionTask_panelTransactionLogID_panelTransactionLogID_FK' is too long
> 
> 
> I had a look into an existing Db (generated early november), and there the FK constraint was named:  
> 
> 	PanelResendTransactionTask_panelTransactionLogID_oid_FK
> 
> which is short enough – and the name schema (SourceTable_sourceAttribute_targetAttribute_FK) makes more sense to me ;-)
> 
> ( I did open a Jira-Ticket: WONDER-634)
> 
> 
> On the other hand:  is there a possibility to limit the size of the FK identifier? I like to have verbose table names ;-)
> 
> 
> 
> regards,
> 
> René Bock
> Software Engineering
> 
> --
> Salient GmbH  -  the interactive advantage
> http://www.salient.de				http://www.openforms.de
> 
> ------------------------------------------------------------------------------
> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
> Tap into the largest installed PC base & get more eyes on your game by
> optimizing for Intel(R) Graphics Technology. Get started today with the
> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
> http://p.sf.net/sfu/intelisp-dev2dev_______________________________________________
> Wonder-disc mailing list
> Won...@li...
> https://lists.sourceforge.net/lists/listinfo/wonder-disc