max 64 keys allowed..

192 views
Skip to first unread message

Stephane Le Dorze

unread,
Oct 14, 2009, 11:16:24 AM10/14/09
to joao.cachopo, fenix-framework
We are experiencing this problem:

com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Too many keys specified; max 64 keys allowed

Looks like it requiers recompiling mySQL..
Any solution? (Joao; I think this is related to the use of inheritance; if so you told me Fenix EDU has a workaround, how to use it?)

Thanks!

Stephane

Stephane Le Dorze

unread,
Oct 18, 2009, 5:39:28 PM10/18/09
to fenix-framework
We had the issue because too much 'subroots' (one per object kind) were related to the main root object (generating the need for a foreign key).
So I've decided to abstract the type of these object (using inheritance and some automatically generated code to manage our needs).
Everything is now more manageable but is clearly an example of "leaky abstraction" (I understand the reasons) but would have not happened.

Joao Cachopo

unread,
Oct 19, 2009, 8:13:25 AM10/19/09
to fenix-f...@googlegroups.com
Stephane Le Dorze <stephane...@gmail.com> writes:

> We had the issue because too much 'subroots' (one per object kind)
> were related to the main root object (generating the need for a
> foreign key).

Hi!

Sorry for not answering before, but it seems that you already solved
your problem.

Still, there is one thing that I would like to know. Are these
troublesome relations 1-to-1 or 1-to-many?

Because, from your email, it seems that they are 1-to-1, and, if they
are, then there is no need of indexes for those foreign keys. At least
not with the latest version of the fenix-framework.

But I believe that the SQL code generator is creating indexes even in
those cases. I'll check this and change it soon.

Best regards,
--
João Cachopo

Stephane Le Dorze

unread,
Oct 19, 2009, 8:45:25 AM10/19/09
to fenix-f...@googlegroups.com
One - One; Indeed! :)

Joao Cachopo

unread,
Nov 1, 2009, 4:11:24 PM11/1/09
to fenix-f...@googlegroups.com

Hi!

Some days ago, after a report of Stéphane that there were many indexes
being generated, and after finding out that there were indexes generated
for 1-to-1 relations, I said that:

> But I believe that the SQL code generator is creating indexes even in
> those cases. I'll check this and change it soon.

The last version of the fenix-framework no longer creates unnecessary
indexes. Now, they are created only for 1-to-n relations.

Stephane Le Dorze

unread,
Nov 4, 2009, 4:10:37 AM11/4/09
to fenix-framework
Thanks, this is greatly appreciated.

2009/11/1 Joao Cachopo <joao.c...@ist.utl.pt>
Reply all
Reply to author
Forward
0 new messages