Re: Has anyone seen a problem with LEFT JOINs in WO 5.2 and MySql?
Re: Has anyone seen a problem with LEFT JOINs in WO 5.2 and MySql?
- Subject: Re: Has anyone seen a problem with LEFT JOINs in WO 5.2 and MySql?
- From: Jonathan Rochkind <email@hidden>
- Date: Wed, 05 Feb 2003 15:00:18 -0600
At 05:14 PM 2/5/2003 +0000, Jonathan Fleming wrote:
The thing is the server already has mySQL and MS SQL Server installed and
the tekkies already know that stuff, so I'm thinking it may save me some
pain in the long run if I go with what they are already running and know.
If I put OpenBase on the server I'll have to deal with every issue of tech
support should it fail on me.... Worring times and i'm lost for answers.
This isn't what you asked, but it's worth considering MS SQL Server if
that's an already existing option on your hosting service. I use MS SQL
Server 7 with WO, and am quite happy with it. I'm using the (payware, but
not unreasonably priced) JTurbo JDBC Driver, with some custom code I've
written to make it work that I've shared before on the lists. But if
you've got MS SQL Server 2000, Apple officially supports it with the free
Microsoft JDBC Driver. (Alas, the free Microsoft JDBC driver is just for
SQL Server 2000).
I have no experience with MySQL though. I'll answer your questions with
regard to MS SQL Server just for the heck of it.
1). How hard is it got get connected to MS SQL Server (are the adapters
readily available)?
We're talking 5.x, right? So it's not an issue of adaptors, it's an issue
of JDBC Drivers (and possibly WO PlugIn class code). If it's MS SQL Server
2000, there's a free microsoft distributed JDBC Driver, and an Apple
provided PlugIn class.
2). How hard is it to learn MS SQL Server for a complete SQL novice like
myself? If it's as easy as learning openBase then no problem. And if it
has a manager interface much like that of OpenBase, then it should be
really easy.
Well, SQL is SQL, more or less. [Sometimes less than more, but nothing
particularly tricky about MS SQL Server.] MS SQL Server has an amazingly
nice management GUI.
3). Is it worth transfering?
I don't know.
4). Will there be a lot of marked changes that will need to be made to the
EOModel and therefore the code? This is important.
You'll have to change the 'external type' for all your attributes. That
should be about it, and you'll always have to do this to change from any db
to another. No big deal really, although somewhat tedious in a large
project. Oh, and the connection dictionaries, naturally.
5). Are there limitations on deployment like OpenBase with licensing
unlimited databases?
Not that I'm aware of.
6). Or, should I best stay where I am and fork out for an OpenBase
License...?
Don't know much about OpenBase, myself, sorry. But I've had very little
trouble with MS SQL Server, like I say. Been using it with WO for a couple
years now.
--Jonathan
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.