<div dir="ltr"><div class="gmail_quote">On Fri, Aug 8, 2008 at 8:58 PM, Jaroslaw Staniek <span dir="ltr"><js@iidea.pl></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
[Let's use (obsolete but working for now) <a href="mailto:kexi-devel@kde.org" target="_blank">kexi-devel@kde.org</a> list. I am responding there.]<br>
<br>
How about using one sequence per table? (otherwise, one commos sequence would not create values starting from 1, what's exactly what users expect sometimes.</blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
<br>
beh->ROW_ID_FIELD_NAME logic is not compatible with our case, I am afraid, so unless I have missed something, KexiDB has to be altered: we need special case in the code where sequence is used. If you can provide one, we could refactor it later using new DriverBehaviour flag.<br>
<br>
How do you like this?<div><div></div><div class="Wj3C7c"><br>
</div></div></blockquote></div>In the end we've just added a "ROW_ID" column to every table using drv_afterInsert and drv_createTable with a sequence so nothing more is needed to be changed on KexiDB.<div><br>
</div><div>For the moment we can create tables (without pk) and insert data on them. <br><br clear="all">Regards,</div><div>Julia<br><br>
</div></div>