use DBI;

Hello to all! I'm new with perl. I'm trying a connection with DBI and a MySQL server. Until here all ok, it works. This little script is executed a lot of times. I've two DB servers and so I would like to implement a simply check: if the connection to the first server is refused, then connect

Re: TZ info used by dB drivers

[EMAIL PROTECTED] wrote: On 7/8/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'm trying to track down how TZ info is used by a dB driver, in this case DBD::Ingres. It would appear that TZ is getting passed to the driver on the first connection (when the driver is installed) and doesn't

Re: TZ info used by dB drivers

[EMAIL PROTECTED] wrote: On 7/8/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'm trying to track down how TZ info is used by a dB driver, in this case DBD::Ingres. It would appear that TZ is getting passed to the driver on the first connection (when the driver is installed) and

float bug? perl 5.8, DBI and oracle 10.2.0

Hi List! I am having trouble with a tricky little beast that smells like a bug, behaves like one but might not be one. Here are the symptoms: I compile perl 5.8.8 (default configuration) and the latest DBI and DBD::Oracle, connect to an Oracle 10.2.0. Then I create one table and insert a number

RE: float bug? perl 5.8, DBI and oracle 10.2.0

Sounds like you're hitting machine epsilon. It is well known that floating point representations aren't exact, and various conversions (e.g. to and from decimal representation) are just going to increase the problem. This is a well known issue people encounter in numerical analysis courses in

Re: Smart way to detect SELECT statements?

Great, exactly what I needed. I did not see the wood for the trees ;-) Thanks, Alexander On 09.07.2007 10:29, Martin Evans wrote: Alexander Foken wrote: Hello DBI-Users, is there a smart way to detect if a prepared statement is a SELECT or a non-SELECT statement? Examine

Re: float bug? perl 5.8, DBI and oracle 10.2.0

On 2007-07-10 14:04:06 +0200, Erwan Lemonnier wrote: I am having trouble with a tricky little beast that smells like a bug, behaves like one but might not be one. Here are the symptoms: I compile perl 5.8.8 (default configuration) and the latest DBI and DBD::Oracle, connect to an Oracle

Re: Smart way to detect SELECT statements?

On 7/10/07, Alexander Foken [EMAIL PROTECTED] wrote: Great, exactly what I needed. I did not see the wood for the trees ;-) Remember that procedures might return values, and might therefore be confused with SELECT statements (eg Informix with EXECUTE PROCEDURE - sometimes; sometimes