6 Nov
2005
6 Nov
'05
4:27 p.m.
On Sun, 06 Nov 2005 12:04:02 -0000, Erwan Arzur <earzur(a)gmail.com> wrote:
Respecting the correct removal/update order in order
to have the
constraint cascading appropriately is a real challenge > in itself, and
we tend to think it is better to rely on the application to maitain data
integrity.
Always the hardest problem and some consider some kinds of referential
integrity to be business rules. However good old Codd's laws reduce the
complexity of updates and deletes.
Now if you want to work on the current database schema
so it follows all
normalization levels, you'd be most welcome, and i'd happily give a hand
!!!
It's about time I did something useful. It seems worth asking whether
you've considered keeping *all* assets with the as static data in a RDBMS
(eg the famous Oracle BLOBS for movies)? I'd expect a DB Schema update
every time a new service is added, even if it's database called "cache".
I've been stealing use cases from as many sources as I can and have
started sketching odd aspects in RelaxNG(compact) towards some core,
generic wiki.
I'm absorbed at the moment in Alloy: integrating it into
round-trip-engineering and automatic test generation, so perhaps I'd
better start by looking at database integrity checks?
I'd be very happy to cooperate with Erwan or anyone on this.
As always great work
Cheers
Jim
--
Jim Stuttard