-
New Commercial Services Section
We have now opened a commercial services section here on the forum for registered users. If you have a Fabrik project that you wish to have someone work on for you, post it under Help Wanted. If you are an application developer and wish to earn some money helping others, post your details under Fabrik Application Developers.
Both of these are unmoderated. It will be up to both parties to work out the details and come to an agreement.
-
Joomla 5.1
For running J!5.1 you must https://fabrikar.com/forums/index.php?wiki/update-from-github/ or include the new file manually https://fabrikar.com/forums/index.php?threads/joomla-5-1-and-fabrik-cannot-find-files-error.54473/post-285151 See also Announcements
dbjoin
- Thread starter arie
- Start date
cheesegrits
Support Gopher
What is the collation set to for the underlying column in your table?
I'm fairly sure if you set the collation correctly, to something like utf8_unicode_ci, then characters should autoatically match their un-accented equivalents.
-- hugh
I'm fairly sure if you set the collation correctly, to something like utf8_unicode_ci, then characters should autoatically match their un-accented equivalents.
-- hugh
rob
Administrator
I tested and its working for me, could you double check you set the field collation of the db join elements 'data->label' something like utf8_general_ci
The one thing that I did find was that if you supplied a default value for the database join element, then in the form view that value would always be used to populate the auto-complete list, rather than being over-ridden by the auto-complete search term. I've fixed that with this commit
https://github.com/Fabrik/fabrik/commit/5fa38d481645afd3fb35d1840edde83677e2bc2a
Apart from that is there any other information that is specific to your database join element ?
-Rob
The one thing that I did find was that if you supplied a default value for the database join element, then in the form view that value would always be used to populate the auto-complete list, rather than being over-ridden by the auto-complete search term. I've fixed that with this commit
https://github.com/Fabrik/fabrik/commit/5fa38d481645afd3fb35d1840edde83677e2bc2a
Apart from that is there any other information that is specific to your database join element ?
-Rob
cheesegrits
Support Gopher
Hmmm. In which case, there's not a lot we can do. That's the whole point of data collation, it defines the rules of how characters get compared, to handle this exact scenario. It's not something which can be handled at the application level (in Fabrik), collation all happens within the database. So it sounds like a MySQL issue.
Have your tried running some SELECT queries by hand on a test table / column, with different collations, and seeing if those work?
-- hugh
Have your tried running some SELECT queries by hand on a test table / column, with different collations, and seeing if those work?
-- hugh