Path: utzoo!censor!geac!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker.mit.edu!bloom-beacon!dont-send-mail-to-path-lines
From: don@zardoz.coral.COM (Don Dewar)
Newsgroups: comp.windows.x
Subject: RDBMS Portability Isses
Message-ID: <9102041510.AA26112@zardoz.coral.com>
Date: 4 Feb 91 15:10:02 GMT
References: <1991Jan28.180523.28946@lgc.com>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 28


We have written an X-based program using X-Windows, Motif, and Ingres.
What we did to help insure portability was to completely separate the
X/Motif code and the Ingres code.  Since we are using g++, we created
p-objects (presentation objects) that implement the UI, and d-objects
(data objects) that access the database.  Every time a pobject needs
data it accesses a dobject.  What this means to us is that if we wrote
very unportable imbedded sql, we only have to change a few methods in
a couple of dobjects.  I guess I really have not answered you
particular question.  What I have told you is how we have written our
code to easily be able to rewrite it for other db's.  

The problem is that all the imbedded SQL I have seen is different from
database to database syntactically.  The SQL statements are the same
of course, but the means of identifying imbedded SQL can be different.



  +---------+
  | Coral   |
  |@@@@@*@**|
  |@@*@@**@@|     Don Dewar
  |*@@**@@@@|     Coral Network Corporation, Marlborough, MA
  |@***@@@@@|     Internet: don@coral.com
  |@@**@@@@@|     Phone:    (508) 460-6010
  |*********|     Fax:      (508) 481-6258
  |Networks |
  +---------+