Is good idea an array of 365 elements in a cell of a table, in order to perform searchs?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

Im having a dude with a new inplementation in a web site.
The ojective is create a search as fast as possible. I have thought two possibilities to do that:

I have several items. Those items has 1 or more of capacity. Each capacity, has several dates (From 1 january to 10 of april, for example). The dates covers 366 days, the current year, and they are indeterminated ranges. Per each date, it has price per day, per week, per15days and per month.

I have designed two possibilities:

First: IdItem StartDate EndDate Capacity PricePerDay PricePerWeek* PricePer15days* PricePerMonth* 1 1-1-2005 10-1-2005 2 100 90 85 80 1 11-1-2005 20-1-2005 2 105 94 83 82 1 21-1-2005 5-2-2005 4 405 394 283 182
   2       ...
Right now arround 30.000 rows, in one year is spected to have 60.000 rows

* In order to compare right, all prices will be translated to days. Example, PricePerWeek will have the Week Price / 7 and go on

Second
IdItem Capacity Days Week 15Days Month Year 1 2 [Array of 365 values, one per day of year] [ .Array. ] [ .Array. ] [ .Array. ] [ .Array. ]
                              ^__ Each item of array its a price

Right now arround 2.500 rows. in one year is spected to have 5.000 rows

I have to compare prices or prices and dates or prices and dates and capacity or capacity and prices

I have no experience working with arrays on a table. Is it fast?
Witch one do u think will have better performance?
Any good idea?

I hope this is enouth information.
Thanks in advance,
Ruben Rubio Rey


[Postgresql General]     [Postgresql PHP]     [PHP Users]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Yosemite]

  Powered by Linux