Provided you stay with the subset of standard SQL supported by Oracle, you can use any local SQL database that Rev understands for your development work. When it comes time to deploy the project, you simply change your (hopefully solitary) database connect statement to point to a different database and you're done.

It really is (at least in most cases) that simple. If your app is really complex and uses a lot of unique features in one DB or another, then the advice doesn't hold.


On Apr 14, 2005, at 4:38 AM, [EMAIL PROTECTED] wrote:

But tell me, suppose I wanted to develop at test applications on my desktop
which would ultimately be intended for Oracle as a back end. Am I better of
trying to get some type of "personal Oracle" (if there is such a thing) for
my desktop... or is there something else I should use for the desktop during
testing, that would not be such a hassle to switch to Oracle once
deployed/distributed?


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Dan Shafer, Co-Chair
RevConWest '05
June 17-18, 2005, Monterey, California
http://www.altuit.com/webs/altuit/RevConWest
EARLY BIRD $70 DISCOUNT ENDS APRIL 15!

_______________________________________________
use-revolution mailing list
[email protected]
http://lists.runrev.com/mailman/listinfo/use-revolution

Reply via email to