Re: Any way to make PG driver obey PrintWarn?


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


I'm using the DBD::Pg driver and i've specifically turned "PrintWarn" off,
yet I am still getting spammed with messages like this:
NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index
...
rt.cpan.org doesn't show any active bugs about this. Is this a known issue?

It is now. :)

This is a bug in DBD::Pg. I just committed a fix to cvs for it, so this will
work properly in version 1.44, which is just around the corner. Thank you
for the report. If you want, you can fill out a bug on rt.cpan.org for it,
but if not, that's fine too.

- --
Greg Sabino Mullane greg@xxxxxxxxxxxx
PGP Key: 0x14964AC8 200602061916
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iD8DBQFD5+cNvJuQZxSWSsgRAtHQAJ46pbdh3SgFak9RvHGu2ZJcOiT7OgCg7p1j
vNiJP5Erc78SEFM45FSQovY=
=p+Sc
-----END PGP SIGNATURE-----


.

Relevant Pages

  • Re: Any way to make PG driver obey PrintWarn?
    ... Greg Sabino Mullane wrote: ... CREATE TABLE / PRIMARY KEY will create implicit index ... No need to file a bug since it's "already" fixed... ...
    (perl.dbi.users)
  • ANNOUNCE: Rose::DB::Object 0.601 released
    ... There have been many changes and bug fixes since the last announcement to ... * Added pre_init_hookmethod to metadata objects and the loader. ... * Added support for bigserial columns. ... * Improved auto-detection of primary key sequence names. ...
    (perl.dbi.users)
  • DBD::Informix test failure for lvarchar - bug found!
    ... LVARCHAR NOT NULL, and only if the table is not a temporary table. ... This bug is now idsdb00139040 in the IBM/Informix CQ database. ... SQL DESCRIPTOR does not handle LVARCHAR NOT NULL properly. ... row_number serial not null primary key, ...
    (perl.dbi.users)
  • Re: for Lynn Trapp RE: two records for one relationship
    ... BTW: your previous concern about a finished good being associated with another finished good has been addresssed. ... "Lynn Trapp" wrote: ... > primary key and the foreign key MUST be the same. ... The code shows a bug when selecting a txtProfileID ...
    (microsoft.public.access.tablesdbdesign)
  • Re: ERROR 515: while creating a merge replication publication
    ... I did as you suggested and manually changed my IDENTITY PRIMARY KEY columns to PRIMARY KEY IDENTITY NOT FOR REPLICATION. ... Every table in the databas has one and only one PRIMARY KEY column now, and they are all created as IDENTITY NOT FOR REPLICATION. ... There is a bug if you have a composite primary key which may generate the error message you are seeing. ...
    (microsoft.public.sqlserver.replication)