From: | Frank Lanitz <frank(at)frank(dot)uvena(dot)de> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Best practice on inherited tables |
Date: | 2013-05-19 09:32:29 |
Message-ID: | 51989C2D.4050106@frank.uvena.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Am 17.05.2013 21:21, schrieb Alfonso Afonso:
> Hi Frank
>
> Although you are thinking in OOP, the SQL is itself one definition
> model that you should not ignore and, IMHO, try to follow the
> normalization statements.
>
> You can build a robust and normalized schema (table primarylocation ,
> table secondlocation that have a idprimarylocation, etc.) and later
> you could build your OOP software translating this to the proper
> classes (in Java you could use a DAO-POJO class or hibernate-jpa, for
> example).
>
> With this solution you can obtain all the benefits of DBRMS besides a
> OOP robust software :)
I was really thinking about this way as it's tradition relational model
and of course kind of a rock stable solution. But I have the fear that
it will end up in a real mess of joins at database layer in the end so I
thought to make usage of such a feature if available ;)
Cheers,
Frank
From | Date | Subject | |
---|---|---|---|
Next Message | Julian | 2013-05-19 11:44:14 | Re: Best practice on inherited tables |
Previous Message | jonranes | 2013-05-19 04:40:04 | Re: PostgreSQL 9.2.3 performance problem caused Exclusive locks |