Thank you everyone for your help! I have spent some time with the MIGXdb plugin. It is a very valuable plugin! I have a few questions I haven't found the answers to in the tutorials... First, are there any tutorials that show how to use custom tables with MIGXdb?
you just need to modify the MIGX-doodles-tutorial for your own tables.
For frontend - stuff you can use rowboat or bloX. BloX can handle also joins and other stuff out of the box or is very extendable.
Need still to create some docs and Tutorials how to use bloX.
Second, with the table structure I have set up, I need to join a few tables together. I noticed under the MIGXdb-Settings that there are Join, Where and Joins fields. What is the syntax to join tables?
lets say, you have some aggregates like that in your schema:
<aggregate alias="Resource" class="modResource" local="category_id" foreign="id" cardinality="one" owner="foreign" />
<aggregate alias="User" class="modUser" local="user_id" foreign="id" cardinality="one" owner="foreign" />
as soon, as you add this to the joins-field:
[{"alias":"Resource"},{"alias":"User"}]
all fields of the joined User and Resource are availiable in the grid
they will have names like Resource_pagetitle or User_username
you can also limit the selected fields by:
[{"alias":"Resource","selectfields":"id,pagetitle,template"},{"alias":"User","selectfields":"id,username,active"}]
or you can join to tables, which are not in your schema:
[{"alias":"Template","classname":"modTemplate","on":"Template.template = myClass.template"}]
Along with that, when I join the tables, both tables have to be in the Xml Schema, right?
its easier, if they are in the same schema, but would also be possible, if they are in different schemas/packages
its possible to have config-php-files with the same name as the configuration either in the migx-configs-folder or in a folder with name 'migxconfigs' in your package-folder, where you could add multiple packages.
While I'm thinking about it, I could extend the code and load multiple packages by a commaseperated list in the packagename-field.
Its of course also allways possible to have custom-processors. MIGXdb will first search in your package-folder for processors, first in a custom-subfolder, then in the default-subfolder, then in the MIGXdb - custom - folder, then in the MIGXdb - default-folder.
☆ A M B ☆
