This is an unfortunate situation, you shouldn't be required to do
this, the people generating your requirements need to be more
informed. I would make damn sure you notify the stakeholders in this
project that the data model is screwed and needs a redesign. I agree
that you should split this table and do a join if you have no option
of redesigning this.
>
> On Tue, Jul 12, 2011 at 4:29 PM, Miguel Angel Conte <diafano@gmail.com> wrote:
>> Yes, sure. I mean, I can't change the whole process which creates columns
>> dynamically.
>>
>> On Tue, Jul 12, 2011 at 6:12 PM, Reinoud van Leeuwen
>> <reinoud.v@n.leeuwen.net> wrote:
>>>
>>> On Tue, Jul 12, 2011 at 03:08:36PM -0300, Miguel Angel Conte wrote:
>>> > Unfortunately It's an inherited data model and I can't make any change
>>> > for
>>> > now...
>>>
>>> but by adding columns you *are* making changes to it...
>>>
>>> Reinoud
>>> --
>>> __________________________________________________
>>> "Nothing is as subjective as reality"
>>> Reinoud van Leeuwen reinoud.v@n.leeuwen.net
>>> http://reinoud.van.leeuwen.net kvk 27320762
>>> __________________________________________________
>>>
>>> --
>>> Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
>>> To make changes to your subscription:
>>> http://www.postgresql.org/mailpref/pgsql-sql
>>
>>
>
