From: Leyne, S. <Se...@br...> - 2004-09-07 18:43:01
|
Leyne, Sean wrote: <metadata> <table name=3D"EMPLOYEE"> <column name=3D"SALARY" type=3D"double" scale=3D"-2" nullable=3D"yes"/> =20 This presentation is 'unexpected' (I didn't expect it). =20 Although "double" is the true datatype, it is not the SQL datatype which I expected to be used in the DDL (i.e. NUMERIC( 10, 2)). Doesn't this representation loose the accuracy of data schema? =20 I haven't a clue what the original DDL looked like, but the database created from the standard employee.fbk file has the employee salary field defined with a double (aka long float) and a scale of -2. I report what I see. =20 <SL> FYI, The original DDL was NUMERIC( 10, 2). =20 <SL> Then what is the use of the schema information in the XML? =20 =20 <SL> By your own words, it doesn't provide true backup/restore functionality; since it doesn't care about maintaining the original schema definition (just a generalization of the datatypes). =20 <SL> The JDBC conventions are more than appropriate for Java and (as you suggest) internal uses, there are plenty of languages where a NUMERIC( 10, 2) and NUMERIC( 15, 2) would have significantly different meanings, due to the data access components. Therefore, the load/dump utility could produce a database which is incompatible with the target application. =20 =20 Remember my stock advice to fledgling language designers: Always pick bad keywords so meddlers have something to change. =20 <SL> Yes, I remember it well! You've gotten me to bite that apple more than once!!!. =20 =20 Sean |