I have created a database of over 200 fields in Calligra Sheets. I successfully imported it into Kexi. If I now want to change one of the fields to "object" instead of "text," I will lose all data after saving. This if fine because there is no data yet. However, once I do the conversion and save it, Kexi deletes all fields past 100. I lose half of my fields. What can I do?
Kexi does not allow importation of "object" fields in a csv file. That is the reason why I have to change "text" to "object" after importation into Kexi.


Thanks,
Kexian
Kexi 2.4.1

Dear Kexian,
Good finding! The limit is 101 (I noted it is a nice prime number for some reason) and never increased but it is only limitation of the Table Designer. I have a fix in the works already to get support for potentially unlimited number of columns.

Just for the record, the only limits will be the underlying database engine, which for SQLite 3 is 2000 by default. It thus easily beats MS Access which supports 255. MySQL offers less depending on used data types, e.g. 256 columns, if each column is a text of max. 256 characters.

But if we agree that database normalization should be the rule, Kexi will warn one day about insanely wide table. I can imagine one case when imported data comes from either denormalized source such as data warehouse sheet or an import from some ancient mainframe. Then of course we could benefit from having support for very long (temporary?) tables as a part of our data processing.

Update: fixed now in 2.6 Pre-RC, and it's planned as addition to 2.5.4 release on November 7th.