Merlin,
> Just curious: why not?
Because it's non-atomic data, which violates normalization and makes
maintenance and data cleaning a royal pain. Also, you'd still need to write
your own operators to be able to do comparisons.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
--
Josh Berkus wrote:
> I don't reccomend using them at any time, though ...
Just curious: why not?
Merlin
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
On Mon, 2 Aug 2004, Josh Berkus wrote:
Suresh,
Is persistant objects and references to these objects
supported in PostgreSQL? If so can anyone point me to
the documentation for these?
These structures are usually known as "Composite Types", although they have a
different, less intuitive name in the
Suresh,
> Is persistant objects and references to these objects
> supported in PostgreSQL? If so can anyone point me to
> the documentation for these?
These structures are usually known as "Composite Types", although they have a
different, less intuitive name in the SQL99 standard which escapes
On Aug 2, 2004, at 2:08 AM, Suresh Tri wrote:
Hi,
Can you have persistant objects in PostgreSQL? In
Oracle you can have create Object types. e.g
create type ADDRESS as object
(street_name VARCHAR2(30),
house_noNUMBER);
In Oracle you can even have references to these
objects from
Hi,
Can you have persistant objects in PostgreSQL? In
Oracle you can have create Object types. e.g
create type ADDRESS as object
(street_name VARCHAR2(30),
house_noNUMBER);
In Oracle you can even have references to these
objects from other tables.
Is persistant objects and refe
