Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the DBD-Oracle CPAN distribution.

Report information
The Basics
Id: 18033
Status: rejected
Priority: 0/
Queue: DBD-Oracle

People
Owner: champoux [...] pythian.com
Requestors: jansson [...] ardendo.se
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 1.16
Fixed in: (no value)



Subject: Query returning gibberisch.
Hello! We ran in to a interesting bug with DBD::Oracle I have attached a small script with a query that will cause DBD::Oracle to return junk, but if you change the query a little (add a space somewhere for example) the query works as it should. This is a little worrying as this could create unknown behaviour for us and we can not be sure if this bug will show up elsewhere. We are using Oracle 10.2 and DBD-Oracle-1.16 perlversion: This is perl, v5.8.6 built for i686-linux-64int On Suse-10 Tell us if you need some more information. Have some more info below. Regards, Johannes Data from ardome_dq_mapping could look something like this: Show quoted text
SQL> select * from ardome_dq_mapping;
ID ---------- DQM_GRO_NAME --------------------------------------------------------------------------------DQM_UNIX_GRO_NAME -------------------------------------------------------------------------------- 21525 Talpa q17776 The tabledefinition of ardome_dq_mapping is made like this: create table ardome_dq_mapping ( id number(20) not null , dqm_gro_name varchar2(32) not null, dqm_unix_gro_name varchar2(32) not null , constraint ardome_dq_mapping_pk primary key (id) using index tablespace ardome_index pctfree 10 initrans 2 maxtrans 255 storage ( initial 2000K minextents 1 maxextents 2147483645 pctincrease 0 ) )tablespace ardome_data pctused 0 pctfree 10 initrans 1 maxtrans 255 storage ( initial 10M minextents 1 maxextents 2147483645 pctincrease 0 buffer_pool default ) logging nocache noparallel; create unique index dqm_1 on ardome_dq_mapping (dqm_gro_name) tablespace ardome_index; create unique index dqm_2 on ardome_dq_mapping (dqm_unix_gro_name) tablespace ardome_index;
Subject: orabug-dbi
Download orabug-dbi
application/octet-stream 1.2k

Message body not shown because it is not plain text.

I have attempted to recreate this bug with little success. I even recreated the Table space and table ect. If Seems my perl likes your code. If you could send me an sql that you know does not work next to one that does and the data the perl script returns this would help. So far the only thing I can see that might be causing this is some sort of encoding in you SQL statement as it seem to work for you when you remove a certain character or two. Look at what you remove and insure it is not an escaped character like ‘ctrl-x’ or alike.
On Tue Mar 07 05:15:14 2006, guest wrote: Show quoted text
> Hello! > > We ran in to a interesting bug with DBD::Oracle > > I have attached a small script with a query that will cause > DBD::Oracle > to return > junk, but if you change the query a little (add a space somewhere > for example) the query works as it should. > > This is a little worrying as this could create unknown behaviour for > us > and we can not be sure if this bug will show up elsewhere. > > We are using Oracle 10.2 and DBD-Oracle-1.16 > > perlversion: > This is perl, v5.8.6 built for i686-linux-64int > On Suse-10 > > > > Tell us if you need some more information. > Have some more info below. > > Regards, > Johannes > > > > Data from ardome_dq_mapping could look something like this: >
> SQL> select * from ardome_dq_mapping;
> > ID > ---------- > DQM_GRO_NAME >
--------------------------------------------------------------------------------DQM_UNIX_GRO_NAME Show quoted text
>
-------------------------------------------------------------------------------- Show quoted text
> 21525 > Talpa > q17776 > > > > The tabledefinition of ardome_dq_mapping is made like this: > > create table ardome_dq_mapping > ( > id number(20) not null , > dqm_gro_name varchar2(32) not null, > dqm_unix_gro_name varchar2(32) not null > , constraint ardome_dq_mapping_pk primary key (id) > using index > tablespace ardome_index > pctfree 10 > initrans 2 > maxtrans 255 > storage ( initial 2000K > minextents 1 > maxextents 2147483645 > pctincrease 0 ) > )tablespace ardome_data > pctused 0 > pctfree 10 > initrans 1 > maxtrans 255 > storage ( initial 10M > minextents 1 > maxextents 2147483645 > pctincrease 0 > buffer_pool default ) > logging > nocache > noparallel; > create unique index dqm_1 on ardome_dq_mapping (dqm_gro_name) > tablespace > ardome_index; > create unique index dqm_2 on ardome_dq_mapping (dqm_unix_gro_name) > tablespace ardome_index; > >
I am trying to clear up the DBD::Oracle rt queue and see there has been no action on this ticket for a long time. Perhaps you found a solution for this problem in which case we'd be interested to know. In view of the age of this rt would be happy for us to close it now? Martin -- Martin J. Evans Wetherby, UK