MYSQL and MSSQL Support

Question

Adobe should really consider building in the option for their advanced clients to run their catalog off a MYSQL or MSSQL database system. The current database implementation for the catalog is just way too slow or perhaps rather badly and clumsily coded. I've been working with databases for years and you should be able to run thousands of transactions in a minute and also access database information in millionths of a second.
For instance you should be able to apply a keyword change to 60,000 image files in under a minute or two and also be able to do this on fairly standard hardware. Currently this type of simple function in Lightroom can take hours.
If Lightroom is to become the defacto industry standard for DAM then we need blistering performance and I firmly believe the product is falling short with it's databasing system and in it's current form cannot stand up to a high end professional production environment.

Answer 1

Hi,
SQL Developers Worksheet has to parse commands to identify their start and finish and their type (query, or update ,... ).
We recognize Oracle SQL , PL/SQL and SQL*Plus , but we have yet to work on other databases syntax.
So at the moment if you running a command against MySQL, SQL Server or Sybase, it has to be fairly similar to an Oracle statement for it to be recognized and run correctly.
EX: SELECT, INSERT,UPDATE,DELETE.
Things like MySQL
+use [databasename]+
or
show databases
are not recognized yet.
Full MySQL recognition will not make it into SQL Developer 3.0 ,
but SQL Developer 3 EA2 (the next release) does allow you to give the Worksheet parser a hint as to what type of statement it is and how to execute it.
The hint is placed in front of the command, and the command has to be terminated with a forward slash on its own line, or a semi colon.
The two hints are
/*sqldev:query*/ if your expecting a result set to be returned
/*sqldev:stmt*/ if you are expecting nothing returned
Example:
If you connect to your MySQL connection you can perform the following
+/*sqldev:query*/show databases;+
+/*sqldev:stmt*/use dermot;+
select database();
+/*sqldev:stmt*/use information_schema;+
select database();
The same goes for SQL Server , Sybase ,.... commands which are not recognized by our Worksheet.
Sybase example:
+/sqldev:query*/sp_help;+
Appreciate this is not an ideal solution, but until we recognize the syntax correctly this may help out.
Just to be clear, we are not supporting all MySQL/SQL Server/Sybase commands yet. But hopefully using a "hint" might be of some use.
Regards,
Dermot.
SQL Developer Team.