Hi!
I have faced with a problem of support of floating-point numbers.
If NLS_TERRITORY set to territory for which a decimal separator is the comma
(for example, CIS) the following code works incorrectly:
CREATE TABLE TEST (A NUMBER(6,2));
INSERT INTO TEST VALUES (2.5);
I've been looking at the way LONGs are handled by DBI and it seems that
the values are always read in full and returned in scalars (except for a
single oracle specific example I found).
Isn't there a better way to handle blobs? One would assume that
databases that implement blobs have a
I'm working in a multi DB environment, and ddd statements prove to be as
unportable as hell, to say the least :)
My scripts however should be able to deal with whatever database (supported by
us) is thrown at it. At current time it is Unify and Oracle.
I'm attaching the beginnings of a module
On Wed, 4 Dec 2002, H.Merijn Brand wrote:
I'm working in a multi DB environment, and ddd statements prove to be as
unportable as hell, to say the least :)
My scripts however should be able to deal with whatever database (supported by
us) is thrown at it. At current time it is Unify and
Driver are free to offer driver specific methods for BLOB handling
(and anything else).
Tim.
On Wed, Dec 04, 2002 at 03:15:26PM +0100, Flemming Frandsen wrote:
I've been looking at the way LONGs are handled by DBI and it seems that
the values are always read in full and returned in scalars
