From: | "Gary Chambers" <gwchamb(at)gmail(dot)com> |
---|---|
To: | |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Query Assistance |
Date: | 2007-12-12 18:00:50 |
Message-ID: | 302670f20712121000w6d3c1ecg39620cfa8c39c606@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
D'Arcy...
> Have you considered this?
I considered integrating the begin and end times into the table. I'm
capturing the data via ACPI events, so it's "transactional" by nature.
I want to be able to keep track of false transitions (hence the
is_outage field).
I'm looking for a way to simplify the transitions output on my web
browser, and I want to combine an offline and a corresponding online
time into a single line.
> I am also thinking of a scheme that uses two tables but I don't really
> know your environment or requirements. I am assuming that you spend
> more time querying the table than updating it. If not your problem
> isn't your database, it's your power plant. :-)
It's nothing complex at all. The power in my neighborhood is
infamously unstable, and I'm merely keep records to complain as much
as I can to the power company.
Thanks for taking the time to reply!
-- Gary Chambers
// Nothing fancy and nothing Microsoft!
From | Date | Subject | |
---|---|---|---|
Next Message | Rodrigo De León | 2007-12-12 19:53:08 | Re: Query design assistance - getting daily totals |
Previous Message | D'Arcy J.M. Cain | 2007-12-12 17:31:29 | Re: Query Assistance |