The MigxDB approach might be a possibility for something short term and quick. but for a long term solution, I would much rather join the relationships on true integer based indexes. Using JSON for extra data in a table is fine but to create relationships, I wouldn't feel comfortable with it long term.
The difference between MIGX and MIGXdb is
MIGX stores its items in one field as a JSON
MIGXdb uses (on true integer based indexes joined) tables to store its items and can be used to create a CMP or as a TV or also for related tables in another MIGXdb.
Bruno,
I installed Migx/MigxDB and having some problems with it. I'm sure it's just my inexperience with the add on and MOdx in general. Couple of questions for you:
1. When I installed Migx, there is a tab called "MIGX", and there are sub-tabs for MigxDB, CMP. I'm not quite sure what to do here. Do I have to generate my package first? From my schema? The order is confusing.
2. How would I create the manager pages
As it stands now, I currently have a schema file created as well as my DB tables. So, how should I proceed with MigxDB? I followed the tutorial and it's still not working out.
Bruno,
I'm assuming you're the author of Migx/MigxDB, correct? There might possibly be a bug. Just something to look into. Try to generate a schema file based on existing tables and it generates a schema file for the entire modx DB. Try to duplicate it. Maybe it's just on my end
seems you are right. thanks for reporting.
Will look into it.
Normaly I don't use it this way.
I do the other way. First creating the schema, then the files.
which tutorial did you follow?