Hi all,
I have two problems with primary key in Kexi:
* Can't set a composite key; two or more columns as primary key.
* Can't set a primary-key vale as Text, it accepts only integer Number.
Are these two problems bugs? or it's a limitation in Kexi and/or SQLite?

anasr wrote:* Can't set a composite key; two or more columns as primary key.
* Can't set a primary-key vale as Text, it accepts only integer Number.
Are these two problems bugs? or it's a limitation in Kexi and/or SQLite?

Hi anasr,
Composite keys are not exposed in Kexi but are available in SQLite. There's a wish reported to support them: https://bugs.kde.org/show_bug.cgi?id=249966, it still has not found its sponsor. Feel free to vote there for the feature.

Similarly, text primary keys are not exposed in Kexi but are available in SQLite. Feel free to file a wish at bugs.kde.org.
See the remark at http://sqlite.1065341.n5.nabble.com/TEX ... p8697.html regarding risks of using text primary keys with SQLite. Other backends can bring their specific issues, I've not checked. Feel free to share your findings.

Kexi generally tries to use common denominator of what's supported in SQL backends. It's possible to add specific features (we do not yet have that) but I think user would be better aware of meaning of such decision.

Kexi's behaviour is (by design) undefined if you use back-end's features (SQLite, MySQL or any other) that are not supported by Kexi. This comes from the fact that Kexi is neither a db administering tool nor a front-end to a specific db back-end.