Hello

    Appart from the numeric mapping, there are other mappings that increase
the compliance with SQL standards. Although those mappings are not necesary,
if will be great if can be added. If the mappings was modified for the
numeric one, perhaps those changes can be easy to do.

The mappings are the following

    SQL92 intermediate

    CHAR VARYING(N)              -- VARCHAR(N)
    CHARACTER VARYING(N)  -- VARCHAR(N)

    SQL92 full

    BIT                                           -- CHAR(1) BYTE
    BIT(N)                                      -- CHAR(N) BYTE
    BIT VARYING(N)                   -- VARCHAR(N) BYTE

    SQL99

    CLOB                                       -- LONG
    BLOB                                       -- LONG BYTE

    I know this is not the first thing in the Todo list, but I hope that at
least can be added to it.

Regards
Blas Rodriguez Somoza

----- Original Message -----
From: "Zabach, Elke" <[EMAIL PROTECTED]>
To: "'Blas Rodriguez Somoza'" <[EMAIL PROTECTED]>; "Paskamp, Marco"
<[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, February 11, 2002 1:37 PM
Subject: RE: Data types and ANSI SQL92 Entry level


> Hi,
>
> starting with 7.3.0.21 NUMERIC and DECIMAL will behave the same with SAP
DB
>
> Elke
> SAP Labs Berlin
>
> > -----Original Message-----
> > From: Blas Rodriguez Somoza [mailto:[EMAIL PROTECTED]]
> > Sent: Montag, 11. Februar 2002 10:29
> > To: Paskamp, Marco
> > Cc: [EMAIL PROTECTED]
> > Subject: Re: Data types and ANSI SQL92 Entry level
> >
> >
> > Hello
> >
> > > It will be possible to modify the database kernel that he
> > knows the type
> > > NUMERIC within "CREATE TABLE"-commands. But inside the
> > kernel this type
> > will
> > > be mapped to FIXED and this will be the value returned by
> > making selects
> > to
> > > the system tables. Will this be a solution?
> >
> >     I think it will be the solution. Up to what I know, to be
> > compliant with
> > the standard it is not necessary that the driver returns a
> > NUMERIC data type
> > identification, mainly because the standard does not provide
> > any facility to
> > get a column data type.
> >
> >     Inside JDBC, the driver can identify the column data_type
> > as "DECIMAL",
> > "FIXED" or any other implementation equivalent data type, without this
> > affecting compliance with the standard.
> >
> >     I think it is better to map the data type in the kernel.
> > In this way,
> > all the interfaces of SAPDB including ISQL will comply with
> > ANSI92 and not
> > only the JDBC one.
> >
> >     The NUMERIC type can have the same type mappings as the
> > DEC[IMAL] one.
> >
> >     The only difference between NUMERIC and DECIMAL that I
> > can see in the
> > standard is that NUMERIC has a precision equal to the one
> > selected in the
> > type declaration and DECIMAL has the same or more precision that the
> > declared one. I believe that for all the SQL implementations
> > I know the two
> > types are exactly the same.
> >
> >     The text that defines the two types in the SQL92 standard is:
> > 17)NUMERIC specifies the data type exact numeric, with the
> > decimal precision
> > and scale specified by the <precision> and <scale>.
> >
> > 18)DECIMAL specifies the data type exact numeric, with the
> > decimal scale
> > specified by the <scale> and the implementation-defined
> > decimal precision
> > equal to or greater than the value of the specified <precision>.
> >
> > Regards
> > Blas Rodriguez Somoza
> >
> > ----- Original Message -----
> > From: "Paskamp, Marco" <[EMAIL PROTECTED]>
> > To: "'Blas Rodriguez Somoza'" <[EMAIL PROTECTED]>
> > Sent: Monday, February 11, 2002 9:23 AM
> > Subject: RE: Data types and ANSI SQL92 Entry level
> >
> >
> > > Hello,
> > >
> > > > -----Original Message-----
> > > > From: Blas Rodriguez Somoza [mailto:[EMAIL PROTECTED]]
> > > > Sent: Freitag, 8. Februar 2002 20:58
> > > > To: [EMAIL PROTECTED]
> > > > Cc: Paskamp, Marco
> > > > Subject: Data types and ANSI SQL92 Entry level
> > > >
> > > >
> > > > Hello
> > > >
> > > >     With the data types and mappings that was included in the
> > > > Reference
> > > > manual, SAPDB is not ANSI SQL92 Entry level compliant, and
> > > > because that the
> > > > JDBC Driver can't be J2EE 1.2 compliant.
> > > >
> > > >     The data types
> > > >
> > > >     NUMERIC
> > > >     NUMERIC(p)
> > > >     NUMERIC(p,s)
> > > >
> > > >     Don't exists and they are required for compliance
> > with SQL92 Entry
> > > > Level.
> > >
> > > Did you mean they are missing in the database kernel or
> > missing in the
> > > MetaData-methods of the JDBC-driver? In the JDBC-driver mappings are
> > > possible.
> > >
> > > >
> > > >     There exists mappings for other types of the SQL92
> > standard (DEC,
> > > > DECIMAL...) but those was apparently forgetted.
> > > >
> > > >     Is it any easy solution to that?
> > > >     I try looking at the source but I don't find how the
> > mappings are
> > > > implemented.
> > >
> > > It will be possible to modify the database kernel that he
> > knows the type
> > > NUMERIC within "CREATE TABLE"-commands. But inside the
> > kernel this type
> > will
> > > be mapped to FIXED and this will be the value returned by
> > making selects
> > to
> > > the system tables. Will this be a solution?
> > >
> > > Regards,
> > > Marco
> > >
> >
> > _______________________________________________
> > sapdb.general mailing list
> > [EMAIL PROTECTED]
> > http://listserv.sap.com/mailman/listinfo/sapdb.general
> >
>

_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general

Reply via email to