Autoincrement fields (in Postgresql terminology smallserial, serial or bigserial) are mapped in the schema correctly to smallint, integer and bigint. If some of these fields is primary key, it is also correctly marked.
But when extracting the information from the Postgresql database, the autoincrement property is not marked at all in the generated schema.
This situation must be corrected, for example by including a new field property (named Serial) and then set it depending upon the information returned by Postgresql. Obviously the function “is_autoincrement” has to be modified. The python module dborm.py has to be modified too, admitting now in the third column the key “PK,SERIAL” for smallint, integer and bigint.
For more explanations, you can read the report
https://github.com/fdesp87/gnatcoll-db/examples/mytests/Report.odt
Autoincrement fields (in Postgresql terminology smallserial, serial or bigserial) are mapped in the schema correctly to smallint, integer and bigint. If some of these fields is primary key, it is also correctly marked.
But when extracting the information from the Postgresql database, the autoincrement property is not marked at all in the generated schema.
This situation must be corrected, for example by including a new field property (named Serial) and then set it depending upon the information returned by Postgresql. Obviously the function “is_autoincrement” has to be modified. The python module dborm.py has to be modified too, admitting now in the third column the key “PK,SERIAL” for smallint, integer and bigint.
For more explanations, you can read the report
https://github.com/fdesp87/gnatcoll-db/examples/mytests/Report.odt