I have a table which stores paths to objects. The path, and framents of the
path, are useful in several different formats. I can store the base path and
have views or code re-render in the variations, or even calc the variations
at update time and store in separate columns. With the last option yes there
is a bit of redundant data, and I suppose calc'd columns could be seen in
the same light. However sometimes this kind of thing is just handy.
Calculated columns would be nice but they're not essential.
Thanks everyone
Joris Dobbelsteen-2 wrote:
>
> http://www.postgresql.org/docs/8.1/interactive/sql-createtable.html
> It does not seem to be listed in the docs if I'm scanning very fast.
> I know Microsoft SQL server supports it.
>
> Perhaps you should use views instead in pgsql.
>
> - Joris
>
>>-----Original Message-----
>>From: pgadmin-support-owner@postgresql.org
>>[mailto:pgadmin-support-owner@postgresql.org] On Behalf Of novnov
>>Sent: donderdag 30 november 2006 3:59
>>To: pgadmin-support@postgresql.org
>>Subject: Re: [pgadmin-support] Can tables have calculated columns?
>>
>>Does no one know the answer to this?
>>
>>novnov wrote:
>>>
>>> I was under the impression that pgsql supported calculated
>>columns in
>>> tables, but don't see a way to implement via pgAdmin and can't find
>>> anything on the subject in the pgsql docs. Are calculated columns
>>> supported?
>>>
>>
>>--
>>View this message in context:
>>http://www.nabble.com/Can-tables-have-calculated-columns--tf271
>>2899.html#a7612700
>>Sent from the PostgreSQL - pgadmin support mailing list
>>archive at Nabble.com.
>>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>
>
--
View this message in context: http://www.nabble.com/Can-tables-have-calculated-columns--tf2712899.html#a7624657
Sent from the PostgreSQL - pgadmin support mailing list archive at Nabble.com.