RE: DBI fetch gets SEGEMENTATION FAULT with new ORACLE date data type(TIMESTAMP WITH LOCAL TIME ZONE).
From: Deepak Gaur (Deepak.Gaur_at_experianems.com)
Date: 10/17/03
- Next message: Tim Bunce: "Re: Named placeholders in DBD::Oracle - bug report"
- Previous message: Dave Rolsky: "ANNOUNCE: Alzabo 0.79_02"
- Next in thread: Tim Bunce: "Re: DBI fetch gets SEGEMENTATION FAULT with new ORACLE date data type(TIMESTAMP WITH LOCAL TIME ZONE)."
- Reply: Tim Bunce: "Re: DBI fetch gets SEGEMENTATION FAULT with new ORACLE date data type(TIMESTAMP WITH LOCAL TIME ZONE)."
- Maybe reply: Deepak Gaur: "RE: DBI fetch gets SEGEMENTATION FAULT with new ORACLE date data type(TIMESTAMP WITH LOCAL TIME ZONE)."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: "'Tim.Bunce@pobox.com'" <Tim.Bunce@pobox.com> Date: Fri, 17 Oct 2003 14:29:48 -0600
Hello Tim,
This seems to have fixed the problem.
Is there a plan to patch it with the next DBD release?
Thanks for your time.
Deepak.
-----Original Message-----
From: Andy Hassall [mailto:andy@andyh.co.uk]
Sent: Thursday, October 16, 2003 4:37 PM
To: Gaur, Deepak; dbi-users@perl.org
Subject: Re: DBI fetch gets SEGEMENTATION FAULT with new ORACLE date
data type (TIMESTAMP WITH LOCAL TIME ZONE).
Gaur, Deepak wrote:
> Hello To All DBI Users :-),
>
> I was trying to use DBI with a new oracle date data type called
> "TIMESTAMP WITH LOCAL TIME ZONE" but the code comes back with a
> "Segmentation Fault(core dumped)" error while trying to fetch data
> from the cursor.
>
> I was just wondering if these new data types are supported in DBI yet
> or I am doing something wrong or there is a different way of handling
> these new datatypes.
>
> I was thinking to migrate all my oracle DB tables using DATE data
> type to TIMESTAMP WITH LOCAL TIME ZONE, so that i can use the
> time_zone session attribute from oracle to get the right local time
> for lot of our international clients. I have our application code in
> both PERL and Java. I m not able to figure out how i can make it to
> work for perl 5.6.1, although Java code seems to accept this new
> date data type without any problems with the new JDBC driver.
>
> Is it just me or is it a known problem?
See this previous thread:
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&threadm=20030514
214011.7170D29873%40chronozon.artofdns.com&rnum=4&prev=/&frame=on
(patch attached to end of my reply, the 2nd message in that thread)
-- Andy Hassall (andy@andyh.co.uk) icq(5747695) (http://www.andyh.co.uk) Space: disk usage analysis tool (http://www.andyhsoftware.co.uk/space)
- Next message: Tim Bunce: "Re: Named placeholders in DBD::Oracle - bug report"
- Previous message: Dave Rolsky: "ANNOUNCE: Alzabo 0.79_02"
- Next in thread: Tim Bunce: "Re: DBI fetch gets SEGEMENTATION FAULT with new ORACLE date data type(TIMESTAMP WITH LOCAL TIME ZONE)."
- Reply: Tim Bunce: "Re: DBI fetch gets SEGEMENTATION FAULT with new ORACLE date data type(TIMESTAMP WITH LOCAL TIME ZONE)."
- Maybe reply: Deepak Gaur: "RE: DBI fetch gets SEGEMENTATION FAULT with new ORACLE date data type(TIMESTAMP WITH LOCAL TIME ZONE)."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
