Suggestion: Fabrik connection ID1 always J! DB

[troester]

It may create some backward compatibility issue.
But I think very few applications are using more than one connection at all
and if they do they usually added a connection and didn't change the ID1 pointing to the J! DB.

Setting connection ID1 to be always the J! DB (i.e. fetching the DB-params from Config, not from the Fabrik table) would stop this "keep in mind to open and resave the connection after installing a backup" etc.

 

[achartier]

Sounds like a good idea to me.

 

[lcollong]

It's a good idea but it should be editable in case. I have at least one app where fabrik's data tables are not in the J! base.
Also we should let several base connection available. I do have a couple app with 2 connections active.

 

[troester]

It's only about the connection with ID1, you still can have multiple connections.

Did you change this one on your site, so it's pointing to some other database?

 

[lcollong]

On all my site except one the connection id1 is pointing on the J! database. On the specifif one, Fabrik was used only to display a list of equipment from an outside DB with search and pagination. No form nor wiew. Only a link to another site with a precharged url.
As far as other connections stay available, I'm ok for dedicating #1 to joomla DB.
I have 3 of my sites using a second connection. But for the third one we are currently replacing direct connection to the DB by api calls and dynamic DBJoin fill.