the attached patch fixes the pgsql clauses to emit sql which works with postgres. Postgres does not (currently) support un-signed integers. Drupal 5 core has added postgres domains to enable use of unsigned integers (smallint_unsigned, int_unsigned, bigint_unsigned). This patch fixes the content.install, content-admin.inc, and content-crud.inc to properly deal with unsigned integers.
(As an aside is doesn't appear that the un-signed nature is used anywhere, but I guess this is just to keep mysql and pgsql in parallel.)
c.
| Comment | File | Size | Author |
|---|---|---|---|
| cck-pgsql-patch | 4.33 KB | carlmuck |
Comments
Comment #1
carlmuck commentedChanged this to a bug (maybe will get picked up :-).
It really is a bug, the distributed code is incorrect for Postgres. The previously submitted patch fixes these db problems.
c.
Comment #2
karens commentedThere are several issues opened about postgres compatibility. I'm going to mark all but one as a duplicate and try to get a working patch that can be tested by those who use postgres. I see the following issues:
http://drupal.org/node/109060, http://drupal.org/node/100546, http://drupal.org/node/106892.
I'm going to mark all but http://drupal.org/node/100546 as duplicates, and work on the patch there, since it seems to be the most complete of the proposed fixes.