[prev in list] [next in list] [prev in thread] [next in thread] 

List:       midgard-dev
Subject:    Re: [midgard-dev] Centralizing metadata handling with MidCOM
From:       Torben Nehmer <torben () nehmer ! net>
Date:       2005-08-18 15:19:56
Message-ID: 4304A71C.1060903 () nehmer ! net
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

- --Piotras wrote on 2005-08-18 17:15:
>> >> Having it in its own table will limit accesses to it when it is needed,
>> >> which would be good for performance reasons.
>> > 
>> > I think we will need access this table with almost every query.
>> 
>> In MidCOM context, this is not true, there are many cases where MidCOM is mostly
>> oblivious to the metadata for many things excluding the currently active object,
>> especially in AIS.
> 
> I also think  about ACL data in such table. 

?


>> > I mentioned repligard table cause I think that using at least three tables
>> > per object update , create or delete is too much.
>> 
>> If this is, what the normalization of the db schema tells us to do, we should do
>> it. It is (almost) that easy IMHO.
> 
> Elaborate please. 

http://en.wikipedia.org/wiki/Database_normalization


Live long and Prosper!
Torben Nehmer

- --
Torben Nehmer, Guenzburg, Bavaria, Germany
http://www.nathan-syntronics.de, mailto:torben@nehmer.net
PGP Public Key: https://www.link-m.de/pgp/t.nehmer.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDBKcbJPh4Kn6d5FYRAi1vAJ9fXJiJiHOche6H3z89/aqloaHJTACgz2wB
4Vx+yPGcwiLmSrH3LIunfM4=
=oS2Q
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@midgard-project.org
For additional commands, e-mail: dev-help@midgard-project.org

[prev in list] [next in list] [prev in thread] [next in thread]