From: Josh Berkus <josh@agliodbs.com>
To: Greg Sabino Mullane <greg@turnstep.com>
To: pgsql-sql@postgresql.org
Subject: Re: SQL Challenge: Arbitrary Cross-tab
Date: Tue, 17 Aug 2004 20:41:09 -0700
Message-ID: <200408172041.09517.josh@agliodbs.com> (raw)
In-Reply-To: <f02adbf424fb41327573d74965e3555b@biglumber.com>
References: <f02adbf424fb41327573d74965e3555b@biglumber.com>
Greg, Stephan,
> (SELECT tid FROM ats WHERE cid=bob.cid LIMIT 1 OFFSET 1) AS tk2,
bzzzzz! Thanks for playing. LIMIT and OFFSET, sadly, are not SQL standard.
They're only portable to MySQL. This has to port to SQL Server and Oracle.
> If that works for 3 (and I think that's standard behavior), then you
> should be able to extend it to any fixed number using the pattern.
Hmmm... that might work. I'll have to test that the nesting doesn't kill SQL
Server (a serious danger) but it's worth a try. Performance will really suck
but fortunately we only run this bill once a month.
--
Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, greg@turnstep.com
Subject: Re: SQL Challenge: Arbitrary Cross-tab
In-Reply-To: <200408172041.09517.josh@agliodbs.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