batonac
Member
Referencing my original question on joins:
And Rob's answer:
I've tried both sharing the same primary key, with primary table id auto-incremental, _extradata not (I believe this is SQL preferred):
Also unique auto-incremental primary keys, with an extra foreign key column in the _extradata table:
I haven't been able to make the first setup work in Fabrik at all. Fabrik likes the second setup better, and allows you to join & edit the two tables together in a single form, as long as new data is not being entered into both forms at the same time.
In other words, in the above example, fabrik will correctly save/associate data in both table2 and table2_extradata together as long as we are editing an entry of table2 that already exists, not adding a new one.
Is there any way around these limitations? Also, do devs view this as a new feature request, or a bug (what's the fixing priority)?
Thanks
Firstly, are one-to-one joins compatible with Fabrik? I'm thinking two tables such as 'school' and 'school_mission_vision' that share the same primary key (entries from the second table are identified by the auto-incrementing primary key in the first table). I see this layout as beneficial for storing additional data for a table that does not need linked to every list where that table is used. Will Fabrik be able to understand/enforce this structure?
And Rob's answer:
One to one joins should work. Create the list pointing at the school db table, then edit it to add the join and ensure that the newly created join's group is not set to be repeatable.
I've tried both sharing the same primary key, with primary table id auto-incremental, _extradata not (I believe this is SQL preferred):
Also unique auto-incremental primary keys, with an extra foreign key column in the _extradata table:
I haven't been able to make the first setup work in Fabrik at all. Fabrik likes the second setup better, and allows you to join & edit the two tables together in a single form, as long as new data is not being entered into both forms at the same time.
In other words, in the above example, fabrik will correctly save/associate data in both table2 and table2_extradata together as long as we are editing an entry of table2 that already exists, not adding a new one.
Is there any way around these limitations? Also, do devs view this as a new feature request, or a bug (what's the fixing priority)?
Thanks