March 24, 2005 at 8:36 am
My I.T. department is working with an geac bd2 system and they can export the information I need to a SQL database. I was planning on using a MySQL database with php to interface between that and my Flash web page. I am signed up for a class dealing with MySQL.
What kinds of diferences are there between working with SQL vs MySQL? Would the things I learn in the MySQL class relate to the SQL database I am going to have to work with?
March 25, 2005 at 2:04 pm
mySQL is definitely more primitive, but all the basic functionality is there. Tables, views, procedures....
The native interface is much more primitive that QA and EM; really just a command line tool. There are a few OS versions of QA, though; some free some not. There's a plug-in for Open Office that's pretty useful...provides an Access like interface.
If you've got money to burn (or paying clients), I'd say SQL 2K is a good choice. Otherwise go with mySQL; it's worth the learning curve. And if you were able to work with php I don't figure you'll have any problems with mySQL.
I'm a big fan of OS products. I use mySQL at home; but at work I use SQL 2K. Pretty much any code you write for mySQL can easily be ported to SQL 2K; but not vice-versa (unless you write SQL like Joe Celko).
Signature is NULL
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply