By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
464,769 Members | 1,165 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 464,769 IT Pros & Developers. It's quick & easy.

Is there a newer version of DBD::Pg?

P: n/a
Pg: 7.4.2

I use perl scripts to import data into my db. When errors occurred
uploading files in Pg ver 7.3.x, $DBI::errstr used to return a row number
from the input file. I could then go to the file make whatever changes and
continue. Since updating to 7.4.2, I no longer receive this information.
I now have to go to psql and run the import and only then will I see the
error row. Is there a newer version than 1.32 of DBD::Pg?

TIA

Patrick Hatcher

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

Nov 23 '05 #1
Share this Question
Share on Google+
4 Replies

P: n/a

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

I use perl scripts to import data into my db. When errors occurred
uploading files in Pg ver 7.3.x, $DBI::errstr used to return a row number
from the input file. I could then go to the file make whatever changes and
continue. Since updating to 7.4.2, I no longer receive this information.
I now have to go to psql and run the import and only then will I see the
error row. Is there a newer version than 1.32 of DBD::Pg?


1.32 is the latest version. If you could provide a sample script that
shows the error you are getting, that would be great. Also, you may be
interested in the DBD::Pg mailing list. Information on the list can
be found at:

http://gborg.postgresql.org/mailman/.../dbdpg-general

- --
Greg Sabino Mullane gr**@turnstep.com
PGP Key: 0x14964AC8 200404211802

-----BEGIN PGP SIGNATURE-----

iD8DBQFAhu+TvJuQZxSWSsgRAlfDAKC86kpKIdj9URwK5DLtVe vs/LVqlwCeLFmd
iALGzPwV5mseJkPiok8Jflk=
=4rss
-----END PGP SIGNATURE-----

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

Nov 23 '05 #2

P: n/a

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

I use perl scripts to import data into my db. When errors occurred
uploading files in Pg ver 7.3.x, $DBI::errstr used to return a row number
from the input file. I could then go to the file make whatever changes and
continue. Since updating to 7.4.2, I no longer receive this information.
I now have to go to psql and run the import and only then will I see the
error row. Is there a newer version than 1.32 of DBD::Pg?


1.32 is the latest version. If you could provide a sample script that
shows the error you are getting, that would be great. Also, you may be
interested in the DBD::Pg mailing list. Information on the list can
be found at:

http://gborg.postgresql.org/mailman/.../dbdpg-general

- --
Greg Sabino Mullane gr**@turnstep.com
PGP Key: 0x14964AC8 200404211802

-----BEGIN PGP SIGNATURE-----

iD8DBQFAhu+TvJuQZxSWSsgRAlfDAKC86kpKIdj9URwK5DLtVe vs/LVqlwCeLFmd
iALGzPwV5mseJkPiok8Jflk=
=4rss
-----END PGP SIGNATURE-----

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

Nov 23 '05 #3

P: n/a
>>>>> "GSM" == Greg Sabino Mullane <gr**@turnstep.com> writes:
I use perl scripts to import data into my db. When errors occurred
uploading files in Pg ver 7.3.x, $DBI::errstr used to return a row number
from the input file. I could then go to the file make whatever changes and


GSM> 1.32 is the latest version. If you could provide a sample script that
GSM> shows the error you are getting, that would be great. Also, you may be
GSM> interested in the DBD::Pg mailing list. Information on the list can
GSM> be found at:

My experience has been that the 1.3x line of DBD::Pg is just plain
broken. On one server running under mod_perl, all placeholder
substituted values were NULL by the time they reached postgres. I've
had other issues with the quote() method returning undef.
Unfortunately those bugs were "not reproduced" even with the full test
cases by the devlopment team.

For my money I'm sticking with DBD::Pg 1.22 since it is completely
stable for me.

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D. Khera Communications, Inc.
Internet: kh***@kciLink.com Rockville, MD +1-301-869-4449 x806
AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to ma*******@postgresql.org so that your
message can get through to the mailing list cleanly

Nov 23 '05 #4

P: n/a
>>>>> "GSM" == Greg Sabino Mullane <gr**@turnstep.com> writes:
I use perl scripts to import data into my db. When errors occurred
uploading files in Pg ver 7.3.x, $DBI::errstr used to return a row number
from the input file. I could then go to the file make whatever changes and


GSM> 1.32 is the latest version. If you could provide a sample script that
GSM> shows the error you are getting, that would be great. Also, you may be
GSM> interested in the DBD::Pg mailing list. Information on the list can
GSM> be found at:

My experience has been that the 1.3x line of DBD::Pg is just plain
broken. On one server running under mod_perl, all placeholder
substituted values were NULL by the time they reached postgres. I've
had other issues with the quote() method returning undef.
Unfortunately those bugs were "not reproduced" even with the full test
cases by the devlopment team.

For my money I'm sticking with DBD::Pg 1.22 since it is completely
stable for me.

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D. Khera Communications, Inc.
Internet: kh***@kciLink.com Rockville, MD +1-301-869-4449 x806
AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to ma*******@postgresql.org so that your
message can get through to the mailing list cleanly

Nov 23 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.