inconsistency between postgres and PEAR?

Heya,

using Postgres and current CVS. The problem is:

- In etc/pgsql.dump the *id columns are created as 'serial'. Postgres
  implicitely creates a sequence called 'table_column_seq',
  e.g. 'bugs_bid_seq'.
- In e.g. postbug.php PEAR is asked for the next ID:
  $id       = $db->nextID('bugs');
  The problem is that PEAR obviously uses 'name_seq' as its name and
  creates e.g. 'bugs_seq'.

The result is that I have two sequences and only one of them is used,
but the other one is referred to from the table design. So I can't drop
either.

Two solutions come to mind: change PEAR or change the pgsql.dump script
to explicitely use sequences that you create by hand.

I'm sorry that I don't send a patch along with this mail - I'm a bit too
lazy for it at the moment ;-)

Mosu

-- 
If Darl McBride was in charge, he'd probably make marriage
unconstitutional too, since clearly it de-emphasizes the commercial
nature of normal human interaction, and probably is a major impediment
to the commercial growth of prostitution. - Linus Torvalds

_______________________________________________
Anthill-workers mailing list
Anthill-workers-+mQDA36h6dWw5LPnMra/[email protected]
http://vmlinuz.ca/mailman/listinfo/anthill-workers

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/7GwHTJ9OsraNuaERAtZxAJ4mReeUhqte9ckVtPvyz40mO0tYhACcCbBN
IYzAp4h8KBlakuHCYeANbzU=
=QnQU
-----END PGP SIGNATURE-----