mySQL currently does not support stored queries or views, though views are
planned in a future version of mySQL according to
http://www.mysql.com/doc/T/O/TODO.html. You can achieve a good speed
increase using mySQL as a back end to Access. The amount of performance
improvement will depend greatly on good use of indexes. Be sure that
anything included in a WHERE clause in an Access linked table is an index
in mySQL. All tables should have primary keys and you'll find that form
interfaces work better if all tables also include a TIMESTAMP(14) column.
We've had very good success with porting Access applications to a mySQL
backend here simply by uploading the tables into the mySQL server and then
re-linking them as ODBC linked tables in Access.
[EMAIL PROTECTED] wrote:
We're looking at moving a web-based application currently built with
Microsoft Access and Cold Fusion to a real database platform. I've only
just started poking around mySQL, so I'm not really up on its capabilities.
One of the things this application relies on fairly heavily is stored
queries (aka stored procedures and/or views, depending on what platform
you're coming from). There are sometimes five or six layers of SQL, with
one query using other queries for their data, between the tables and what
the user eventually sees. Poking around the documentation, it appears that
mySQL doesn't support that sort of thing. Do I have that right, or am I
missing something important? Even if I can't get deeply layered queries
with mySQL, is there a relatively painless way of building them with some
other tool (say, php or perl and the appropriate modules)? Am I likely to
get a significant boost to performance if I keep Access in the middle for
queries but move the tables to mySQL?
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
