the ORDER BY, which is not of much use as adding an ORDER
> BY jumbles them up. Duh!
LIMIT in PostgreSQL applies *after* ORDER BY, so you won't have this
problem :)
--
Cliff Crawford http://www.sowrong.org/
birthday party cheesecake jellybean BOOM
---(e
:date + '2 months 10 days'::interval;
?column?
2000-03-11 00:00:00-05
(1 row)
--
Cliff Crawford http://www.sowrong.org/
birthday party cheesecake jellybean BOOM
---(end of broadcast)---
TIP 5: Have y
* Cliff Crawford <[EMAIL PROTECTED]> menulis:
>
> SELECT table2.title_no, table2.paidto_date
> FROM table1, table2
> WHERE table1.title_no=table2.title_no
> AND (date_part('month', table1.effect_date) !=
> date_part('month',
27;month', table1.effect_date) !=
date_part('month', table2.paidto_date)
OR date_part('day', table1.effect_date) !=
date_part('day', table2.paidto_date));
(At least, I think that will work, but I never trust any SQL I write
without thorou
