⚠ In case you've missed it we are migrating to our new website, with a brand new forum. For more details about the migration you can read our blog post for website migration. This forum is read-only and soon will be archived. ⚠


Member Since 19 Sep 2012
Offline Last Active Sep 20 2012 08:01 PM

Posts I've Made

In Topic: set_relation_n_n very slow

19 September 2012 - 03:17 PM


I myself also found that the CRUD does not work usable enough (browser goes off for some time etc.) if I try to use the n:n-relation on something like "authors" to an "book".

There are many, many Authors in the Author-table (>60k), but just to e.g. edit a Book (looking up the related Authors like 1, 2 or 3 in the relation-table and then showing the names (better would be: being able to build something to show "Name, First Name" because many Authors have the same last Name)) should not consume so much time etc.

It seems every single Author is loaded somewhere in the background - and that is not neccesary and seems to be the problem.

Does anybody has an idea about that?


In Topic: Priority Field Relation in the set_relation_n_n function

19 September 2012 - 03:13 PM

Interesting: I asked myself the same question (what is this field for). As I understood it it comes from a special use case and does add some nice funtionality (drag'n'drop to reorder the persons). But allow me the suggestion that it could be explained also in the API - maybe one time very clear for all..