On 6/20/06, Steve Ellenoff <[EMAIL PROTECTED]> wrote:
Can you clarify what you mean about it being easier to detect what's
changed via insert/delete as you mention here? I'm a bit
confused.. maybe an actual example of some code would clarify what
you mean? I'm planning on moving to mysql in the near future too, so
am curious as well.
Sorry, I'm deep inside a client problem today and am probably typing
shorthand as incomprehensible as someone we all know (g,d&rfws...)
Table fred has a M:M relationship with lookup table fredtypes via the
many-to-many link table fred2types. Operator does maintenance on the
fred record and uses a multi-select list box to add a couple new
fredtype attributes, leave a couple alone and de-select a couple of
obsolete ones.
In the VFP world, in the interest of avoid PACKing whenever possible,
you write some arcane logic to figure out which fredtypes links stayed
the same, which can be switched to point at other fredtype records
('cause the old one is deleted and a new one was added), which M:M you
want to add, and which you need to delete without updating. This is
hellish coding.
In MySQL (and every other data engine without the RECALL command),
PACKing is rarely if ever needed, so you can DELETE the whole batch of
fred2types M:M records and create a new set without concern.
--
Ted Roche
Ted Roche & Associates, LLC
http://www.tedroche.com
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
