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: 55445
Status: resolved
Priority: 0/
Queue: DBD-Oracle
People
Owner: Nobody in particular
Requestors: bohica [...] ntlworld.com
Cc:
AdminCc:
Bug Information
Severity: Normal
Broken in: 1.24a
Fixed in:
  • 1.25
  • 1.25-withoutworldwriteables
  • 1.25_brokentar
  • 1.26

History Show all quoted text
  Wed Mar 10 12:38:39 2010 bohica [...] ntlworld.com - Ticket created
Subject: get_info(28) SQL_IDENTIFIER_CASE seems to return the wrong value
perl -MDBI -le '$h = DBI->connect("dbi:Oracle:host=xxx.easysoft.local;sid=devel","xxx","xxx");print $h->get_info(28);' returns 3 which is SQL_IC_SENSITIVE described as: Identifiers in SQL are case-sensitive and are stored in mixed case in system catalog. I thought it should be SQL_IC_UPPER: Identifiers in SQL are not case-sensitive and are stores in uppercase in system catalog. drop table mje; drop table "mje"; create table mje (a int); select * from mje; no rows selected select * from "MJE"; no rows selected drop table mje; create table "mje" (a int); select * from "mje"; no rows selected select * from "MJE"; table or view does not exist select * from mje; table or view does not exist Same applies to column names as they are also identifiers. The value 3 (SQL_IC_SENSITIVE) appears to be right for SQL_QUOTED_IDENTIFIER_CASE (93). Martin -- Martin J. Evans Wetherby, UK
  Fri Apr 23 12:30:50 2010 champoux [...] pythian.com - Correspondence added
I think this is a DBI issue as both SQL_IC_UPPER and SQL_IC_SENSITIVE are found there not in DBD::Oracle? On Wed Mar 10 12:38:39 2010, MJEVANS wrote: Show quoted text
> perl -MDBI -le '$h = > DBI-
> >connect("dbi:Oracle:host=xxx.easysoft.local;sid=devel","xxx","xxx");print
> $h->get_info(28);' > > returns 3 which is SQL_IC_SENSITIVE described as: > > Identifiers in SQL are case-sensitive and are stored in mixed case in > system catalog. > > I thought it should be SQL_IC_UPPER: > > Identifiers in SQL are not case-sensitive and are stores in uppercase > in > system catalog. > > drop table mje; > drop table "mje"; > create table mje (a int); > select * from mje; > no rows selected > select * from "MJE"; > no rows selected > drop table mje; > create table "mje" (a int); > select * from "mje"; > no rows selected > select * from "MJE"; > table or view does not exist > select * from mje; > table or view does not exist > > Same applies to column names as they are also identifiers. > > The value 3 (SQL_IC_SENSITIVE) appears to be right for > SQL_QUOTED_IDENTIFIER_CASE (93). > > Martin
  Fri Apr 23 12:30:52 2010 The RT System itself - Status changed from 'new' to 'open'
  Fri Apr 23 12:30:52 2010 champoux [...] pythian.com - Status changed from 'open' to 'rejected'
  Fri Apr 23 12:36:03 2010 bohica [...] ntlworld.com - Correspondence added
On Fri Apr 23 12:30:50 2010, PYTHIAN wrote: Show quoted text
> I think this is a DBI issue as both SQL_IC_UPPER and SQL_IC_SENSITIVE > are found there not in DBD::Oracle?
I don't but I'll look into it. Each DBD should provide its own get_info. Martin -- Martin J. Evans Wetherby, UK
  Fri Apr 23 12:36:07 2010 The RT System itself - Status changed from 'rejected' to 'open'
  Fri Apr 23 15:10:24 2010 champoux [...] pythian.com - Correspondence added
On Fri Apr 23 12:36:03 2010, MJEVANS wrote: Show quoted text
> On Fri Apr 23 12:30:50 2010, PYTHIAN wrote:
> > I think this is a DBI issue as both SQL_IC_UPPER and SQL_IC_SENSITIVE > > are found there not in DBD::Oracle?
> > I don't but I'll look into it. Each DBD should provide its own get_info. > > Martin
After fixing the other type one 'Finally' I am not sure where this would be set in DBD::Oracle?? any guess on where it should be set??
  Mon Apr 26 04:06:30 2010 bohica [...] ntlworld.com - Correspondence added
On Fri Apr 23 15:10:24 2010, PYTHIAN wrote: Show quoted text
> On Fri Apr 23 12:36:03 2010, MJEVANS wrote:
> > On Fri Apr 23 12:30:50 2010, PYTHIAN wrote:
> > > I think this is a DBI issue as both SQL_IC_UPPER and SQL_IC_SENSITIVE > > > are found there not in DBD::Oracle?
> > > > I don't but I'll look into it. Each DBD should provide its own get_info. > > > > Martin
> > After fixing the other type one 'Finally' I am not sure where this would > be set in DBD::Oracle?? > > any guess on where it should be set?? > > > >
I believe this is the relevant code http://search.cpan.org/~timb/DBI-1.609/lib/DBI/DBD.pm#Generating_the_get_info_method. I'll see if I can generate it today. Martin -- Martin J. Evans Wetherby, UK
  Mon Apr 26 04:21:30 2010 bohica [...] ntlworld.com - Correspondence added
On Mon Apr 26 04:06:30 2010, MJEVANS wrote: Show quoted text
> I believe this is the relevant code > http://search.cpan.org/~timb/DBI- > 1.609/lib/DBI/DBD.pm#Generating_the_get_info_method. > I'll see if I can generate it today. > > Martin
Try the attached file for a start. Might need to go through them and check each one but it is better than the default values I am getting now. It is missing: SQL_MAXIMUM_STMT_OCTETS SQL_MAXIMUM_STMT_OCTETS_DATA SQL_MAXIMUM_STMT_OCTETS_SCHEMA and I've no idea what values they should have. I also had to change SQL_SERVER_NAME to 'unknown' as it showed my database name. Martin -- Martin J. Evans Wetherby, UK
Subject: x.pl

Message body is not shown because it is too large.

  Fri May 07 15:04:09 2010 champoux [...] pythian.com - Correspondence added
Ok I have applied that stuff on Trunk http://svn.perl.org/modules/dbd-oracle/trunk give it a test and I will close it cheers John On Mon Apr 26 04:21:30 2010, MJEVANS wrote: Show quoted text
> On Mon Apr 26 04:06:30 2010, MJEVANS wrote: >
> > I believe this is the relevant code > > http://search.cpan.org/~timb/DBI- > > 1.609/lib/DBI/DBD.pm#Generating_the_get_info_method. > > I'll see if I can generate it today. > > > > Martin
> > Try the attached file for a start. Might need to go through them and > check each one but it is better than the default values I am getting > now. It is missing: > > SQL_MAXIMUM_STMT_OCTETS > SQL_MAXIMUM_STMT_OCTETS_DATA > SQL_MAXIMUM_STMT_OCTETS_SCHEMA > > and I've no idea what values they should have. I also had to change > SQL_SERVER_NAME to 'unknown' as it showed my database name. > > Martin
  Fri May 07 15:04:10 2010 champoux [...] pythian.com - Status changed from 'open' to 'resolved'
  Fri May 07 15:06:39 2010 bohica [...] ntlworld.com - Correspondence added
On Fri May 07 15:04:09 2010, PYTHIAN wrote: Show quoted text
> Ok I have applied that stuff on Trunk > > http://svn.perl.org/modules/dbd-oracle/trunk > > give it a test and I will close it > > cheers > John
Will do but it will have to wait until Monday now - sorry. Show quoted text
> On Mon Apr 26 04:21:30 2010, MJEVANS wrote:
> > On Mon Apr 26 04:06:30 2010, MJEVANS wrote: > >
> > > I believe this is the relevant code > > > http://search.cpan.org/~timb/DBI- > > > 1.609/lib/DBI/DBD.pm#Generating_the_get_info_method. > > > I'll see if I can generate it today. > > > > > > Martin
> > > > Try the attached file for a start. Might need to go through them and > > check each one but it is better than the default values I am getting > > now. It is missing: > > > > SQL_MAXIMUM_STMT_OCTETS > > SQL_MAXIMUM_STMT_OCTETS_DATA > > SQL_MAXIMUM_STMT_OCTETS_SCHEMA > > > > and I've no idea what values they should have. I also had to change > > SQL_SERVER_NAME to 'unknown' as it showed my database name. > > > > Martin
>
-- Martin J. Evans Wetherby, UK
  Fri May 07 15:06:41 2010 The RT System itself - Status changed from 'resolved' to 'open'
  Mon May 10 04:07:51 2010 bohica [...] ntlworld.com - Correspondence added
On Fri May 07 15:06:39 2010, MJEVANS wrote: Show quoted text
> On Fri May 07 15:04:09 2010, PYTHIAN wrote:
> > Ok I have applied that stuff on Trunk > > > > http://svn.perl.org/modules/dbd-oracle/trunk > > > > give it a test and I will close it > > > > cheers > > John
> > Will do but it will have to wait until Monday now - sorry.
Done and it works now - thanks. Martin -- Martin J. Evans Wetherby, UK
  Fri May 28 13:06:56 2010 champoux [...] pythian.com - Correspondence added
confirmed fixed
  Fri May 28 13:06:57 2010 champoux [...] pythian.com - Status changed from 'open' to 'resolved'
  Tue Dec 21 19:07:58 2010 champoux [...] pythian.com - Fixed in 1.25 added
  Tue Dec 21 19:07:58 2010 champoux [...] pythian.com - Fixed in 1.25-withoutworldwriteables added
  Tue Dec 21 19:07:58 2010 champoux [...] pythian.com - Fixed in 1.25_brokentar added
  Tue Dec 21 19:07:58 2010 champoux [...] pythian.com - Fixed in 1.26 added