Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

TeeJay (2309)

TeeJay
  (email not shown publicly)
http://www.aarontrevena.co.uk/

Working in Truro
Graduate with BSc (Hons) in Computer Systems and Networks
pm : london.pm, bath.pm, devoncornwall.pm
lug : Devon & Cornwall LUG
CPAN : TEEJAY [cpan.org]
irc : TeeJay
skype : hashbangperl
livejournal : hashbangperl [livejournal.com]
flickr :hashbangperl [flickr.com]

Journal of TeeJay (2309)

Wednesday March 22, 2006
05:35 AM

more postgres lameness

[ #29069 ]

Just as I thought Postgres' quirky behaviour was having less of an impact on development I hit this lame barrier :

SELECT DISTINCT ON expressions must match initial ORDER BY expressions

It's entirely reasonable to want unique by pk, but order by a date field, thats' the kind of thing we use databases for, but no - Postgres requires that the distinct restriction matches the order by.

Very lame and incredibly annoying

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Of course ugly hack of a work around (which btw is how I'd describe Slony ;p), is to copy and paste the whole of your order by clause into the uniqueness clause. lame lame lame lame.
    --

    @JAPH = qw(Hacker Perl Another Just);
    print reverse @JAPH;