Hi All,
I am a new comer on postgres world and now using it for some serious (at
least for me) projects. I have a need where I am running some analytical +
aggregate functions on data where ordering is done on Date type column.
From my initial read on documentation I believe internally a date
Dhimant Patel drp4...@gmail.com writes:
From my initial read on documentation I believe internally a date type is
represented by integer type of data. This makes me wonder would it make any
good to create additional column of Integer type and update it as data gets
added and use this integer
This makes me wonder would it make any good to create additional column of
Integer type and update it as data gets added and use this integer column for
all ordering purposes for my sqls - or should I not hasitate using Date type
straight into my sql for ordering?
Keep in mind what
Dhimant Patel drp4...@gmail.com wrote:
I am a new comer on postgres world and now using it for some
serious (at least for me) projects. I have a need where I am
running some analytical + aggregate functions on data where
ordering is done on Date type column.
From my initial read on
On Thu, Apr 28, 2011 at 12:17 AM, Kevin Grittner
kevin.gritt...@wicourts.gov wrote:
Dhimant Patel drp4...@gmail.com wrote:
I am a new comer on postgres world and now using it for some
serious (at least for me) projects. I have a need where I am
running some analytical + aggregate
Thanks for all valuable insights. I decided to drop the idea of adding
additional column and
will just rely on Date column for all ordering.
Tom - thanks for clear answer on the issue I was concerned about.
Maciek,Kevin -
thanks for ideas, hint on generate_series() - I will have to go through cpl
