realbasic-nug
[Top] [All Lists]

Re: REALSQLdatabase Classic limitation

To: REALbasic NUG <realbasic-nug at lists dot realsoftware dot com>
Subject: Re: REALSQLdatabase Classic limitation
From: Phil M <phil at mobleybros dot com>
Date: Wed, 30 Aug 2006 14:12:50 -0700
Delivered-to: listarchive at realsoftware dot com
Delivered-to: realbasic-nug at lists dot realsoftware dot com
References: <F0FED9A3-8996-4103-AC5C-5B11288B2292 at mobleybros dot com> <p06230915c11ba9adf223 at [10 dot 1 dot 1 dot 2]>
On Aug 30, 2006, at 1:59 PM, Dr Gerard Hammond wrote:

I think you will have to conditionally compile them into the separate binary.

I created a database wrapper and let it conditionally build in any appropriate plugin libraries depending on build time constants. It has all the same calls as the RB database object. It has one property theDatabase as cDatabase. This gets cast to whatever the appropriate database type is. The wrapper now handles 12 databases types, including all the data syntax differences, connected users differences etc etc etc.

Thinking through this problem, I was planning on building my own database wrapper which would pick the appropriate engine. What I was planning on doing is just creating a generic Database object as the variable, but what I cannot figure out is how to cast without forcing an unsupported database engine to be compiled. At least on the Macintosh OS X, it is feasible for either database engine to be used; even if the REALdatabase is only used to convert from the old format to the new format.

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>


<Prev in Thread] Current Thread [Next in Thread>