Hello!
Database mariadb.
Driver mariadb ODBC connector for MS Windows 32-bit latest installed, in wine control ODBC base is selected and connected using the driver. Connection name visible in sparx, i select it, test connection = succseeded. And it doesn't work ..
Hi,
First, I prefer using code-weavers crossover. If you are going to invest money in a product like EA, you should also consider crossover. It allows you to set up your EA once. It does not need to be re-built/reinstalled when you change distros or perform EA updates, as it does most if not all of the of the prerequisite installation for you (e.g. fonts, Jet etc.). You can save yourself some hassle there, such as multiple versions of EA, so you can make try the latest update without messing up a working setup.
My checklist is something like:
in linux:
- setup username password and database access permissions.
- run schema creation and schemea population scripts
- use sql command line client from user running EA, check you can access the EA model.
In Wine
- (crossover) create bottle backup of working ea setup
- install ODBC drivers (from crossover app menu)
- setup system ODBC DSN according to the Sparx instructions,
- to debug connection.
- Enable 'GLOBAL' ODBC logging options in System DSN window, and enable 'Tracing' ODBC logging in tracing tab- Move on with successful 'test connection'
With all of that in place, tweak the connection string to setup the provider. E.g. My Postgres connection string looks something like:
LocalPG --- DBType=4;Connect=Provider=MSDASQL.1;Persist Security Info=True;Data Source=LocalPG;LazyLoad=1;
With a working setup, i then use crossover to create another EA backup to baseline my working Postgres setup.
