Not disagreeing about the bug - but:
A "serial" data type in PostgreSQL is syntatic sugar for "integer NOT NULL
DEFAULT nextval('some_sequence'::regclass)" combined with the implicit
creation of a sequence used in the DEFAULT clause.
So the D&D function *do* create the correct base type for the column, but
fails to create the corresponding sequence and default clause for the
column.
2015-12-21 15:31 GMT+01:00 Paolo Cavallini <[email protected]>:
> Hi all,
> when D&D between different DBs, a SERIAL column is silently converted
> into a int4, and trying to modify the table through the DB Manager edit
> table tool throws an error. To me this seems a bug, anyone disagrees?
> Thanks.
> --
> Paolo Cavallini - www.faunalia.eu
> QGIS & PostGIS courses: http://www.faunalia.eu/training.html
> _______________________________________________
> Qgis-developer mailing list
> [email protected]
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
--
Med venlig hilsen
Bo Victor Thomsen
_______________________________________________
Qgis-developer mailing list
[email protected]
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
