EIdNotSetException with Bigint(identity) starting 0!

[wlandgraf (Wagner Landgraf)]

@Lahann_Kai

To me it looks like Aurelius treats an identity value of 0 as not set.

Correct.

@Lahann_Kai

I'd like to agree with that, but then DataModeler should set up the type accordingly.

I'm afraid I don't understand what you mean here?

If zero is a valid id value for your database, then you should make to tell Aurelius so, using IdUnsavedValue, as discusses in a few topics:

ID not set on entity class and sequencer definitions

You can. Use the IdUnsavedValue attribute to set a default 'unsaved id' different from zero. [Entity] [IdUnsavedValue(-1)] // <-- insert this line. [Table('employee')] [Description('')] [Sequence('employee_id_seq')] [Id('FId', TIdGenerator.IdentityOrSequence)] TEmployee = class(TMoonshineObject) (***) HTH,

existing Identifier with zero value

Hi Kounalakis, Yes, it's possible, just add this mapping to Entities that have integer key fields where value may by zero: [IdUnsavedValue(-1)] TMyEntity = class You may use -1 or any other value (that will not exists as valid Id on your table) to represent unsaved entities. Regards,