For what it's worth the Revelation / Arev / OpenInsight crowd have a thing called "Bonding" where in you can create a bond with another database structure, and natively list/sort/query that database. Bundled with Arev comes Dbase / Ascii bonds. I don't know what comes with OI, but I believe you get bonds for all manner of database(s).
As far as I remember, the emphasis is on data movement _from_ the other data structure, altho' it handles creation of data within that structure, but only within the rules of that structure - ie you can't create multivalues within a normalised base, and it's up to your programming to convert mv files into flat form based files. The best people to ask about this sorta thing have got to be Sprezzatura (Andrew McAuley and co) at www.sprezzatura.co.uk -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dawn M. Wolthuis Sent: 15 April 2004 02:04 To: 'U2 Users Discussion List' Subject: RE: Jbase handles multivalue on RDBMS Do you know if there is a flavor of the type-it-in multivalue query language (e.g. UniQuery) that can be executed against data stored in Oracle, DB2, SQL Server, etc? I know that DataBASIC can be with jBASE and ONGroup, for example. --dawn Dawn M. Wolthuis Tincat Group, Inc. www.tincat-group.com Take and give some delight today. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of djordan Sent: Thursday, April 15, 2004 12:27 AM To: 'U2 Users Discussion List' Subject: Jbase handles multivalue on RDBMS Hi Steve Just to correct you, jbase does not require you to move to 1NF files to run on an RDBMS. Jbase will port multi dimensional data across to an RDBMS and automatically handle the conversion to multiple tables invisible to the application. The issue is in the quality of the dictionary, like lengths and data types that RDBMS do not handle breaking the rules. Jbase does handle a lot of these issues and I would assume IBM will incorporate that in U2. Also in such an environment you would not move all your files over to an RDBMS, it would make sense to leave work files and control files in Universe which are usualy the worst offenders. If you wish to make your application portable in a future environment like this, look at SQLising your files including multivalues and starting cleaning your data as this will be your biggest issue, not multivalues. Just another point, jbase does the same for Cache, which is another multi-dimensional database, although not PICK. Regards David Jordan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Mayo Sent: Thursday, 15 April 2004 4:01 AM To: U2 Users Discussion List Subject: RE: The future of U2 The way that jBase handles the problem is by requiring the database be flattened out (i.e., no multivalues) and strict data typing. This is of course the standard with 1NF databases. Unfortunately for most of us, it means a complete redesign of the existing mv database structure. Over the past several years, all new systems that I have developed have used 1NF. Still most of the data still uses multivalues and would take years to convert. :-) Steve -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
