Hallo,
in my project I can use 6 extern tables. If I try to use one more, then I can store, but openening kexi again, the connections are lost.
Albrecht

Hi Albrecht, confirmed.

I have a sample kexi file to attach there; a buggy SQL generated is as follows (see the double , ,):

SELECT "table".id, "table".a, "table".b, "table".c, "table".d, "table".e, "table".f, __kexidb_table1_0.a, , __kexidb_table3_2.c, __kexidb_table4_3.d, __kexidb_table6_4.f, __kexidb_table7_5.g, "table".OID FROM "table" LEFT OUTER JOIN table1 AS __kexidb_table1_0 ON "table".a=__kexidb_table1_0.id LEFT OUTER JOIN table2 AS __kexidb_table2_1 ON "table".b=__kexidb_table2_1.id LEFT OUTER JOIN table3 AS __kexidb_table3_2 ON "table".c=__kexidb_table3_2.id LEFT OUTER JOIN table4 AS __kexidb_table4_3 ON "table".d=__kexidb_table4_3.id LEFT OUTER JOIN table6 AS __kexidb_table6_4 ON "table".e=__kexidb_table6_4.id LEFT OUTER JOIN table7 AS __kexidb_table7_5 ON "table".f=__kexidb_table7_5.id ORDER BY "table".id

Correction: the above error comes from the fact that I missed one Visible Column value in the design:



When I filled that, the table opens OK.

Hoewever upon record inserting I am getting this:



It also happens e.g. for 4 combo columns, not just 6. Despite the error message, records gets inserted, when you re-open the table you can note that.

So what I find is a different issue than what I understood from your report. Thanks anyway and feel free to add more comments.
My test file is here: http://kexi-project.org/download/tests/Combos-ok.kexi

Update: the issue I found above is not related to any limits. It's related to not "escaping" names in specific place when name is a reserved word.

My table in the test above was called "table" so special escaping is needed to make the name different from the TABLE SQL keyword because Kexi uses SQL internally. Now I am fixing this (for 2.9.11-POST - not to be released, and for current 3.0 alpha).

For the list of reserved words see https://userbase.kde.org/Kexi/Handbook/ ... rved_Words

Albrecht, Is this the case for you too?

Reported at https://bugs.kde.org/show_bug.cgi?id=364810

Related bug reported: https://bugs.kde.org/show_bug.cgi?id=364811 "Error opening table with missing visible column of lookup filed"

Hi Jaroslaw,

I think there could be yet another problem.
I had inserted not such a reserved word ("visibly column" is not empty)
Sending you an image with http://home... went wrong.
Are you interested in the DB?

Yes I am interested in your db (can be shared privately).