Subject: | |
From: | |
Reply To: | |
Date: | Mon, 24 Mar 2003 15:01:26 EST |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
In a message dated 3/24/03 9:31:35 AM Pacific Standard Time,
[log in to unmask] writes:
> This is not necessarily as simple as it seems. Which RDBMS are you
> targeting?
Agreed! In addition to issues with regard to which SQL RDBMS, there can be
issues as to scope of a conversion/migration. SQL is different from Image in
many ways. A set of decisions need to be made as to how much the structure
of a database will be changed to utilize SQL functionality that does not
exist within Image. For example, this morning, I was doing some DB design
work, defining a few data elements as 'boolean'. Unless I've already
forgotten some Image knowledge, I can't do that in Image.
Related topic:
For those who are far more knowledgeable about std SQL than me, is there any
way in SQL to define data elements (columns) INDEPENDENTLY of any specific
table? That's a good feature of Image that I was disappointed to find out is
apparently lacking in SQL.
Wayne
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
|
|