From: | Michael Ansley <Michael(dot)Ansley(at)intec-telecom-systems(dot)com> |
---|---|
To: | "'Kenn Thompson'" <KThompson(at)adestagroup(dot)com> |
Cc: | "'pgsql-sql(at)postgresql(dot)org'" <pgsql-sql(at)postgresql(dot)org> |
Subject: | RE: Object features of pg |
Date: | 2000-10-03 14:52:50 |
Message-ID: | 7F124BC48D56D411812500D0B747251406144E@fileserver002.intecsystems.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Hi, Kenn,
>> It seems that if you want to define a type address that
>> you will need more than a reference in another table. I
>> see what you're trying to do, but don't understand the
>> advantage of having a type address. Especially when you
>> seem to be using standard SQL to manipulate the data anyway.
I'm not sure how postgres does it, but I think that it might actually store
the address in the address table, and use an oid to reference it from the
client table. The reason for doing this is that a) it matches the way an
object orientated language would map it, and b) it should be a LOT faster
than using a foreign key lookup. My understanding is that using OIDs is way
faster than using FKs, which is where ODBs get their speed from. So, if I
can do objects like ODBs in postgres then I get the speed of an ODB with the
funcionality of a relational database (functions, sql, rules, etc.)
Of course, I could just use the address OID as an FK on client, but that
would only really be going half the distance.
That's the plan, anyway.
Cheers...
>>
>> >>> Michael Ansley
>> <Michael(dot)Ansley(at)intec-telecom-systems(dot)com> 10/03/00 09:25AM >>>
>> No. I want the address attribute of the client class to
>> be of type address,
>> which is defined by the address table. Perhaps I should
>> have named things a
>> little more clearly ;-)
>>
>>
>> >> -----Original Message-----
>> >> From: Kenn Thompson [mailto:KThompson(at)adestagroup(dot)com]
>> >> Sent: 03 October 2000 15:15
>> >> To: Michael(dot)Ansley(at)intec-telecom-systems(dot)com
>> >> Subject: Re: [SQL] Object features of pg
>> >>
>> >>
>> >> Shouldn't that be
>> >> create table address (address varchar(50), postcode
>> varchar(9));
>> >> create table client(id integer, name varchar(30), address
>> >> varchar(50);
>> >> ?
>> >>
>> >> >>> Michael Ansley
>> >> <Michael(dot)Ansley(at)intec-telecom-systems(dot)com> 10/03/00
>> 08:14AM >>>
>> >> I've done the following:
>> >>
>> >> create table address (address varchar(50), postcode
>> varchar(9));
>> >> create table client(id integer, name varchar(30),
>> address address);
>> >>
>> >> Now, how the hell do I get information into the address
>> >> field of client?
>> >> There appears to be very little in the manual dealing with
>> >> PGs object
>> >> features. Any pointers to places in the manual, or direct
>> >> instructions
>> >> would be gratefully accepted.
>> >>
>> >> Cheers...
>> >>
>> >> MikeA
>> >>
>> >>
>>
From | Date | Subject | |
---|---|---|---|
Next Message | David Diller | 2000-10-03 14:59:48 | table as field type?? |
Previous Message | Michael Ansley | 2000-10-03 14:25:43 | RE: Object features of pg |