--- macky <macky(at)edsamail(dot)com> wrote:
> im still in the dark when it comes to postgres.....
> is there a way i can
> know if there was a new entry on a table...
That's a pretty common problem.
> scenario...
>
> i have a script that runs every 5 minutes... that
> script checks if there's
> a new entry in that table... and if YES there's a
> new entry ill do some
> processing...
Probably the most straightforward thing to do is to
simply insert a timestamp in each row as it is added
to the database. That way you can do a simple select
to figure out which rows have been added:
SELECT * FROM my_table WHERE insert_time > now() - '5
minutes'::interval
or alternatively
SELECT * FROM my_table WHERE insert_time > '2001-08-03
11:30'
The best part is that creating a column that includes
a timestamp automagically is fairly easy to do.
Simply define your table like this:
CREATE TABLE foo (
insert_time timestamp DEFAULT CURRENT_TIMESTAMP,
name text
);
Once your table is created you simply insert into
table foo ignoring the insert_time column like so:
INSERT INTO foo (name) VALUES ('Jason');
and your timestamp automagically gets inserted:
processdata=> SELECT * FROM foo;
insert_time | name
------------------------+-------
2001-08-03 11:32:48-06 | Jason
(1 row)
Pretty neat, huh?
> is there an internal utility that i can use in
> postgres that can tell me
> that this rows a new commers... hehehe....
Nope, you have to come up with the logic yourself.
However, PostgreSQL has all kinds of tools that are
really helpful.
> if someone has other ideas on how to deal with this
> speak out...
>
> thanks in advance......
>
> btw..
> my idea is that that table will have an addtional
> column as reference
> lets say column "READ" 1 for yes 0 for NO
>
That would work too, but it would be a lot harder.
For example, you would have to first select all the
rows where READ is 0, do your processing, and then
update all of those rows to 1. You would almost
certainly want to do all of this in a transaction so
that you could roll READ back to 0 if something went
wrong, and you would probably want to lock the table
to boot as you would have to worry about your
processing step taking more than 5 minutes. If it
did, the second transaction would see the last 10
minutes of of inserts as being unread even though the
first transaction was still working on them.
I hope this is helpful,
Jason
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/