Re: [phpslash-users] On sequences... ah...

[Ajay S. <ss...@od...>]

> I looked at the code for nextid() in db_pgsql.inc of PHPlib and
> compared that with db_mysql.inc. PHPlib uses PostgreSQL's CREATE
> SEQUENCE command for nextid() so it won't be troublesome. I did a
> dump of my postgresql tables and saw the CREATE SEQUENCE statements
> generated, so the db_sequence table seems to be unnecessary in
> PostgreSQL.  I'll play with it and let you know which works best.

Wowa.. you must be using the 7.3-dev version of PHPLIB because my
db_pgsql.inc doesn't even have a nextid function.  I know it was added
later on though.  

> I also need to know why our INTs are of the various sizes INT(11),
> INT(15) in particular so I know what PostgreSQL counterpart to put
> in the tables. Right now, I just stuck in int4's in place of int(11)
> and int8's in place of INT(15). What's the range for these ints in
> MySQL? Is int(11) an 11 byte integer, or an 11 digit integer?

You can probably credit this to the inconsistancies in the DB structure.
I don't think any id's should be a different range then the others.

> I'm not submitting any patches yet since I'm still figuring out
> where the MySQL/PostgreSQL/SQL92/SQL3/*SQL statements differ and
> making placeholders for DB agnostic switches. I'm getting there
> though. :) I've got rc1 basically functional at
> http://gra.ph/~xenos/phpslash-0.6-rc1 and am redoing the table
> structures for rc2 with refinements in mind.

Fantastic.  I don't think there was too many query changes between rc1
and rc2.

later,
ajay
----------------------------------------------------------------
Satyajot (Ajay) Sharma 
ss...@od...
Digital Odyssey System Administrator
"There's more than gravity pushing on me" --Folk Implosion
----------------------------------------------------------------