• Hello Fabrik Community

    Fabrik is now in the hands of the development team that brought you Fabrik for Joomla 4. We have recently transitioned the Fabrik site over to a new server and are busy trying to clean it up. We have upgraded the site to Joomla 4 and are running the latest version of Fabrik 4. We have also upgraded the Xenforo forum software to the latest version. Many of the widgets you might have been used to on the forum are no longer operational, many abandoned by the developers. We hope to bring back some of the important ones as we have time.

    Exciting times to be sure.

    The Fabrik 4.0 Official release is now available. In addition, the Fabrik codebase is now available in a public repository. See the notices about these in the announcements section

    We wish to shout out a very big Thank You to all of you who have made donations. They have really helped. But we can always use more...wink..wink..

    Also a big Thank You to those of you who have been assisting others in the forum. This takes a very big burden off of us as we work on bugs, the website and the future of Fabrik.

Databasejoin element return error on list & detail view

Aurore

New Member
Hello !
I need help, i might miss something !
I try to create a databasejoin element connecting to another database (which is entered in Connection tab)
My form is on DB A, my databasejoin connect to DB B and choose my regions table.

Everything working great on form : The databasejoin's dropdown showing me every regions.

But on list & details view, i got a 500 and a 1146 error, even if there is no raw on the table.

I just want to be sure : Can i create a databasejoin element to another database ?
If not, do you have an idea of how can i get those values ?

I tried in case to create List's Join and related data but i didn't made it work.
Thanks in advance !
 
We don't support cross database joins. So your joined table has to be on the same database as your form.

The only workaround for this would be to create a MySQL view on your form's database, which does something like ...

DEFINE VIEW regions AS SELECT * FROM dbB.regions

... so you essentially have a copy of the regions table on dbA. It would be "read only", so you couldn't add rows to it, but would work as a simple lookup table.

-- hugh
 
We are in need of some funding.
More details.

Thank you.

Members online

Back
Top