Re: DBIx::Recordset : DBD::Pg 1.39 bind_param issues

2003-12-29 Thread Rudy Lippan
On Sun, 28 Dec 2003, Terrence Brannon wrote: > It looks like we are in some sort of (painful?) symbiotic relationship > here. As I update my drivers to make sure that Recordset works before > release, I keep having problems. Looks like it. But hey, anything that finds bugs is a good thing, IMO.

Re: DBIx::Recordset andLongNames error

2003-12-29 Thread Terrence Brannon
Kaare Rasmussen wrote: do you mean will recordset update across multiple tables? I can't remember. Also this. Would be something of a dream, though I'm not sure its doable. I think the big problem with doing something like this is that updates to multiple tables

Re: DBIx::Recordset andLongNames error

2003-12-29 Thread Kaare Rasmussen
Hi > Can I run it somehow? I will compile a test case and send it to you. > I think Angus Lees creates such a patch... I think I missed when > upgrading Recordset though... Angus? This would add miles to the usability of DBIx::Recordset > do you mean will recordset update across multiple table

Re: DBIx::Recordset andLongNames error

2003-12-29 Thread Terrence Brannon
Kaare Rasmussen wrote: I've run into an error with DBIx::Recordset and !LongNames. My query involves several tables: so_invoicebatch LEFT JOIN so_invoice USING (batchnr) LEFT JOIN so_orderhead ON (so_invoice.ordernr=so_orderhead.ordernr) LEFT JOIN co_custaddr_v USING (contact_id)

DBIx::Recordset andLongNames error

2003-12-29 Thread Kaare Rasmussen
I've run into an error with DBIx::Recordset and !LongNames. My query involves several tables: so_invoicebatch LEFT JOIN so_invoice USING (batchnr) LEFT JOIN so_orderhead ON (so_invoice.ordernr=so_orderhead.ordernr) LEFT JOIN co_custaddr_v USING (contact_id) LEFT JOIN co_country