That is exactly what I am saying ;-)
I just noticed that this behaviour started between WOLips 3.3.5195
and WOLips 3.3.5205. Version 5195 did not display this error. I just
tested it on another system. (5.4.2-ish).There I got the same
behaviour.
Fixed.
ms
On 2 jun 2008, at 11:07, Alexander Spohr wrote:
Johann,
it sounds like you got it the wrong way ’round.
Am 02.06.2008 um 08:58 schrieb Johan Henselmans:
I am creating a n:m relation between two tables, called adminuser
and admingroup, and flatten the relationship.
That would result in an
Johann,
it sounds like you got it the wrong way ’round.
Am 02.06.2008 um 08:58 schrieb Johan Henselmans:
I am creating a n:m relation between two tables, called adminuser
and admingroup, and flatten the relationship.
That would result in an n:m table, admingroupadminuser, with two
relatio
I am creating a n:m relation between two tables, called adminuser and
admingroup, and flatten the relationship.
That would result in an n:m table, admingroupadminuser, with two
relationships on both sides: one would propagate the primary key to
the table admingroupadminuser, the other one w
