Re: How to model searchable properties of an entity
From: Rene Hartmann <rehartmann_at_t-online.de>
Date: Tue, 17 Aug 2004 22:01:10 +0200
Message-ID: <Pine.LNX.4.33.0408172158220.2005-100000_at_linux.local>
> Seems that there is some psychological problem about it. OO
> Programmers feel good if they have all their data in a single "object", no
> matter how complex that objects is and of how many sub-objects it is
composed of. To them, a row in a relational table is
> a kind of "object", so they feel uncomfortable if data is spread over
> several rows. Joining these rows together appears a clumsy operation to
> them, though it's logically a simple operation and also not necessarily
> a slow one. (Though it may sometimes be slow in practice)
Date: Tue, 17 Aug 2004 22:01:10 +0200
Message-ID: <Pine.LNX.4.33.0408172158220.2005-100000_at_linux.local>
I´m sory - somehow a line was deleted from my posting, so I fix it here:
>
> Seems that there is some psychological problem about it. OO
> Programmers feel good if they have all their data in a single "object", no
> matter how complex that objects is and of how many sub-objects it is
composed of. To them, a row in a relational table is
> a kind of "object", so they feel uncomfortable if data is spread over
> several rows. Joining these rows together appears a clumsy operation to
> them, though it's logically a simple operation and also not necessarily
> a slow one. (Though it may sometimes be slow in practice)
-- Rene´ HartmannReceived on Tue Aug 17 2004 - 22:01:10 CEST