Re: Max column number.

From: Kevin Crain <kevin(dot)crain1(at)gmail(dot)com>
To: pgsql-sql(at)postgresql(dot)org
Subject: Re: Max column number.
Date: 2011-07-13 18:07:58
Message-ID: CADwm0agTW3KZDN1UvzUcqBWUnmEGkWaja4Jyv1DXAVZ56nm-DQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Is there any room for improvement in the data types?

On Wed, Jul 13, 2011 at 11:03 AM, Miguel Angel Conte <diafano(at)gmail(dot)com> wrote:
> I have the metadata in the same csv.
>
> On Wed, Jul 13, 2011 at 3:00 PM, Kevin Crain <kevin(dot)crain1(at)gmail(dot)com> wrote:
>>
>> How are you determining the data types for these columns?
>>
>> On Wed, Jul 13, 2011 at 8:45 AM, Miguel Angel Conte <diafano(at)gmail(dot)com>
>> wrote:
>> > Hi,
>> > Thanks for your interest. This app load scv files which change every day
>> > (sometimes the columns too). The sizes of these files are in avg 15MB.
>> > So,
>> > We load something like 100MB each day. We tried to find a better
>> > solution
>> > but we couldn't, becouse one of the our requirement is not to use a lot
>> > of
>> > space. Also, the app is used to consult these information, and for our
>> > particular type of select's queries, we get the best performance if the
>> > information is all into a same row.
>> >
>> > On Wed, Jul 13, 2011 at 3:28 AM, Kevin Crain <kevin(dot)crain1(at)gmail(dot)com>
>> > wrote:
>> >>
>> >> I still can't imagine why you'd ever need this...could you explain
>> >> what this does? I'm just curious now....
>> >>
>> >> On Tue, Jul 12, 2011 at 10:55 PM, Kevin Crain <kevin(dot)crain1(at)gmail(dot)com>
>> >> wrote:
>> >> > 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(at)gmail(dot)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(dot)v(at)n(dot)leeuwen(dot)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(dot)v(at)n(dot)leeuwen(dot)net
>> >> >>> http://reinoud.van.leeuwen.net kvk 27320762
>> >> >>> __________________________________________________
>> >> >>>
>> >> >>> --
>> >> >>> Sent via pgsql-sql mailing list (pgsql-sql(at)postgresql(dot)org)
>> >> >>> To make changes to your subscription:
>> >> >>> http://www.postgresql.org/mailpref/pgsql-sql
>> >> >>
>> >> >>
>> >> >
>> >
>> >
>
>

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Kevin Crain 2011-07-13 18:20:33 Re: Max column number.
Previous Message Miguel Angel Conte 2011-07-13 18:03:45 Re: Max column number.