I have a table with an INSERT/UPDATE/DELETE statement trigger. The
trigger's action is to insert "jobs" into a queue noting that the table
has changed.
A number of other tables have FK relationships with this table, and they
have their own statement triggers that fire on DELETE.
When I delete
> select * from
> (select distinct on (storenumber), itemsku, storenumber,price
>from storeproduct where itemsku='10001'
>order by storenumber, price) ss
> order by price;
>
> regards, tom lane
Thanks tom, this is working. I never thought it could be done like this.
yudie
>
> --
On Tue, Oct 26, 2004 at 16:23:20 -0400,
Wei Weng <[EMAIL PROTECTED]> wrote:
> In the following query
>
> SELECT Parent FROM Channels ORDER BY Parent ASC;
>
> If I have a couple of (NULL)s in the field [Parent], they will be listed at
> the bottom of the query result.
>
> Is it because Postgre
On Wed, 27 Oct 2004, Dmitry P. Ovechkin wrote:
> Hello.
> I'mtrying to implement history tables using rules.
> I have
> test_table
> --
> create sequence history_seq start 1;
> create sequence test_sequence;
> # source table
> drop table test_table;
> create table test_table (
> i integer
Hello.
I'mtrying to implement history tables using rules.
I have
test_table
--
create sequence history_seq start 1;
create sequence test_sequence;
# source table
drop table test_table;
create table test_table (
i integer default nextval('test_sequence'),
c character(10)
);
# history table
c
