On Mon, Jun 30, 2003 at 01:51:03PM +0200, Henrik Tougaard wrote: > David Coulthart skrev: > > > We recently migrated our site from DBI-1.21 to 1.37 and have noticed > > that our DBD::Ingres installation broke. We were running > > DBD::Ingres-0.32, but I also attempted to upgrade to 0.36 and am > > having the same problem during make test. The problem relates to > > using do() to execute a statement. From the make test attempt with > > 0.36: > > > > t/dbi......Modification of non-creatable hash value attempted, > > subscript "Statement" at blib/lib/DBD/Ingres.pm line 116. > > > > A colleague of mine has put up a bug report at > > http://rt.cpan.org/NoAuth/Bug.html?id=2738 > > > > IMHO, it looks like this problem has to do with some sort of interface > > change to DBI b/w 1.21 and 1.37. Does anyone know what the details of > > this change would be and what the proper fix for the DBD::Ingres > > module would be? > > > This pussles me, as did the tr.cpan bug report. I have just tried to install > Ingres2.6, perl 5.8.0, DBI 1.37 and DBD::Ingres 0.36 on a clean Linux box. > No problems - at all. > But looking at the DBI docs I can see that $dbh->{Statement} should be > read-only, which rules out my setting a value on it.
The 'read only' actually only relates to applications not drivers. (Although in fact applications can also set Statement currently.) > Why doesn't it fail for me, but for you? I just don't get it! > What OS, Ingres and perl versions do you use? - That might give a clue. A DBI trace may help. And send me the code around Ingres.pm line 116. Tim.
