Trying to install the twitter module on PostgreSQL, I got errors on unknown type numeric_unsigned. I fixed this by creating the 'numeric_unsigned' as alias of the 'int' type, but didn`t work, since the new type doesn`t accept precision and scale parameters.
To fix all the problems, i solved by replacing all the 'numeric' fields in the schema with integer ones, and removing their precision and scale parameters. I`m not sure it is the best way to do that, but it works now..

I`m attaching a patch with the modifies i did on twitter.install.

CommentFileSizeAuthor
twitter-postgres.patch1.22 KB-redShadow-

Comments

-redShadow-’s picture

-redShadow- commented
Title: Bugged schema for PostgreSQL » Buggy schema for PostgreSQL
Issue tags: +PostgreSQL

Not already fixed: I am esperiencing other problems using the module on PostgreSQL. I`ll investigate and try to find a way to fix that. (Errors are not really meaningful, I have to debug a bit).

mikl’s picture

mikl
Location Møn
commented
Status: Patch (to be ported) » Needs work

But why use numeric at all, when bigint will do?

john franklin’s picture

john franklin commented

+1 need.

I'm running twitter module 2.6 with PostgreSQL and I'm hitting this problem. Rather than convert to int (triggers the bug below), make them signed numeric and all is well. Mostly. Postgres complained about a relation it didn't like. Might have been a fluke here, but it looked like twitter_uid was numeric in one table and int in another, which Postgres didn't like.

#491794: Twitpocalypse bug (will not import if twitter_id greater than 2,147,483,647)
*sigh* I can't wait until Tue Jan 19 03:14:07 2038.

rukaya’s picture

rukaya commented

So the attached patch doesn't work? I've encountered the same error when trying to install with postgres.

rukaya’s picture

rukaya commented

In the install file I changed all instances of 'type' => 'numeric' with 'unsigned' => TRUE to 'unsigned' => FALSE, and it now seems to install and work fine.

For everyone else who finds this : http://drupal.org/node/513578

steinmb’s picture

steinmb commented
Status: Needs work » Closed (works as designed)

Fixed in this core issue #256001: pgsql driver does not handle unsigned numeric fields