Daniel Brooks wrote:
I've been using DBIx::Recordset for a while now, and it's been great.
Yes, Recordset is great :)
However, just the other day I started adding some new functionality to my program, and I've started getting this error message:
[Fri Dec 12 09:06:29 2003] [error] [client 4.63.107.173] Premature end of script headers: purchase.pl
[Fri Dec 12 09:06:29 2003] [error] [client 4.63.107.173] [Fri Dec 12 09:06:29 2003] purchase.pl: Error executing run mode 'add_item': DBD::ChurlPg
ChurlPg???? ah:
http://archives.postgresql.org/pgsql-interfaces/2003-02/msg00005.php
You know, now that you mention it, I thought I was using DBD::Pg. I'll have to check my setup, since this is test machine is a bit newer than my production machines.
only knows about the pg_type attribute at /usr/lib/perl5/site_perl/5.8.0/DBIx/Database.pm line 148.
That message is coming from DBD::ChurlPg's dbdimp.c
// XXX this is broken: bind_param(1,1,{TYPE=>SQL_INTEGER}); if (attribs) { if (sql_type) croak ("Cannot specify both sql_type and pg_type");
if ((svp = hv_fetch((HV*)SvRV(attribs),"pg_type", 7, 0))==NULL) croak("DBD::ChurlPg only knows about the pg_type attribute");
I wish we had a confess so we could actually trace the execution stack closer.
Sure. How do I get a stack trace?
Anyone know what's going on?
A lot of what Recordset does depends on what driver you use. I don't know what's going on but it might have to do with not knowing anything about ChurlPg.
db48x
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
