AppGini Community Forums

Somebody has idea why this happened?

I think it happened in all my tables with field "ref" as unique.

No idea on that, DevGiu, but to help out others who may find this post...

I've found it works best in AppGini to use a field named 'id'. AppGini will detect this and automatically set it up to be the primary key field. It's the first field I add when defining a table.

Even when I know I'll have other fields that could be primary, I still let AppGini create the primary key using 'id'. The other field that might have been suitable as primary, I make that field required and unique.

Just a preference, of course, but one I've found makes AppGini work more smoothly.

It's a bug, recognized by AppGini Team.

In my situation, if you look at it, "id" is my PK, the other field is just a varchar field with UNIQUE index.

LOL @ ME

Too early in the morning I guess. Completely overlooked that you had 'id' as primary. All those refs to ref overwhelmed me