rlucassen wrote:
Just installed LLBLGEN Pro 4.2 May 2016.
This is the latetest 4.2 i can find.
Still no luck i can't use ulong in combination with Sequence -> LAST_INSERT_ID
I Want to use a type converter to converte between a bigint and ulong
When using the Typeconverter all goed well except the part when a new entity is created it does not have an id.
I think this is the part where the LAST_INSERT_ID should kick in but because i can't select is it does always return 0 as id.
true, I can reproduce this. As soon as the types don't match or when a type converter is needed, the sequence is no longer settable. If both types (entity field type and db field type) are equal, be it ulong, decimal whatever, the sequence is settable.
We'll look into this.
Btw, you don't need to specify an unsigned bigint to use an unsigned bigint sequence in MySQL. No-one is going to insert (2^64)-1 rows in a table before the end of time. 2^64 is 18446744073709551616. If you insert every 1ms 1 row, it will take 213503982335 days before you run out of keys. Which is 584942417 years.
If you use a signed bigint, it will be a ulong in mysqldirect and will map to an ulong, no type converter needed.
Using an unsigned bigint as PK is seriously overkill in this and the requirement of a typeconverter especially makes it more complex than needed.