Search:

I have now fixed that issue in RC8.

There seems to be an issue using seqno() with tables opened exclusively. I will look into it and fix it. It works shared.

No it is in RC7.

The next Seqno() is maintained in the table header. It is not reset at app startup.

Additionally, each row (record) inserted into a Lianja table has a hidden readonly column called SYNCNUM which is used internally, but it can be referenced in your apps too.

GUID() is another...

I should also mention that this handles concurrent requests while maintaining that the result is guaranteed unique. The original question you asked about using SELECT MAX() ... Is not guaranteed to...

Seqno() operates in a similar way to AUTOINC and returns a unique row id.