From: Gary Chambers <gwchamb@gmail.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Query Assistance
Date: Wed, 12 Dec 2007 13:00:50 -0500
Message-ID: <302670f20712121000w6d3c1ecg39620cfa8c39c606@mail.gmail.com> (raw)
In-Reply-To: <20071212123129.ad22c7ce.darcy@druid.net>
References: <302670f20712120858k210dd812l8b232ce98d5d162f@mail.gmail.com>
<20071212123129.ad22c7ce.darcy@druid.net>
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!
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: gwchamb@gmail.com
Subject: Re: Query Assistance
In-Reply-To: <302670f20712121000w6d3c1ecg39620cfa8c39c606@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox