Hi,
Is there any plans for Laserfiche Server to support MySQL as the base DBMS in the near future?
I understand that MySQL can only be referenced to for lookup purposes for LF Modules.
Looking forward for the reply. Thanks.
Hi,
Is there any plans for Laserfiche Server to support MySQL as the base DBMS in the near future?
I understand that MySQL can only be referenced to for lookup purposes for LF Modules.
Looking forward for the reply. Thanks.
No, we don't have any plans to support MySQL. What advantages do you see, other than cost? And what is your take on the fragmentation of the community between MySQL and MariaDB?
I can live with MS SQL Server for the base DBMS and was glad to see that Workflow supports ODBC (MySQL, MariaDB or PostgreSQL) to do external table lookups/queries.
However, it doesn't make sense that ODBC is NOT supported for external tables in LF templates or forms. It should be quite easy for the LF developers to roll this into the product.
Are there any plans to support ODBC in LF Templates or Forms?
How/where can customers submit enhancement requests for this functionality?
We have a lot of authoritative data sitting in MySQL and PostgreSQL databases. Why?
Cost, performance and web applications support.
The fragmentation in the MySQL and MariaDB communities is not really an issue since MariaDB is binary compatible with MySQL. Even if it weren't ODBC support would make it irrelevant anyways.
Creating a view in SQL Server that references a linked MySQL should work, although I haven't tested it. Please see http://www.ideaexcursion.com/2009/02/25/howto-setup-sql-server-linked-server-to-mysql/ for a step-by-step guide on setting up a linked server. Once that's done, creating a view which exposes the data you want LFS to query should be straightforward.
Direct access of external databases by lfs.exe is planned for a future release.
I had read about setting up a linked server to do this in other LF Answers threads but wasn't familiar or confident enough with SQL Server to try it. Thanks for the link with detailed instructions, I may give it a shot now.
Using SQL server as a "proxy" to MySQL via ODBC is really hacky and inefficient way to retrieve data where performance and safety/stability may be considerations.