0 (zero) as ID breaks the App

[Drazen D. Babic]

Hi all, 

this might be interesting for someone, the problem is table which has ID as:

0

1

2

...

This ID is NOT the primary key as autoincrement one, but the plain INTEGER.

As seen, the ID=0 exist and this is where Jam will fail to create/update the record, even though it is set to use ID as the primary key (there is no other INT to use).

The problem is, this is Imported table, and the ID=0 is referenced in other tables.

Which basically breaks the Jam App since ID=0 is here to stay, can't be touched.

Thoughts?

Regards

D.