I do see your points regarding the existence of use cases for this
feature, and I agree that at worst, the implementation of this feature
would provide a way to greatly simplify query design and at best provide
a whole new method of obtaining decision supporting data from a
relational
Naz Gassiep wrote:
Let us not do the same to
SQL and implement SKYLINE on our own, only to have other DBMS vendors
implement it in different ways and then finally when the SQL standard
includes it they try to make some kind of average approximation of the
implementations resulting in *none*
Shane Ambler [EMAIL PROTECTED] writes:
If we consider this thoroughly and compile a suitable syntax that covers
all bases it could be used as the basis of the standard definition or be
close to what ends up in the standard.
I'll bet you a very good dinner that the word SKYLINE will never be
Few things from our side:
1. 'Skyline Of' is a new operator proposed in ICDE 2003, one of the topmost
conferences of Data Engineering. Skyline operation is a hot area of research
in query processing. Many of the database community people do know about
this operator, and it is fast catching the
Gavin,
Personally, I'd love to see some of these newer data analysis
capabilities added to PostgreSQL -- or at least put out there as
interesting patches.
I think if the code is good enough, and we can avoid horrible non-standard
syntax extensions, they should go in. We have to defend our
Josh Berkus josh@agliodbs.com writes:
I think if the code is good enough, and we can avoid horrible non-standard
syntax extensions, they should go in. We have to defend our title as most
advanced database and having stuff like Skyline first (before DB2 or MS)
goes a long way for that.
The query Ranbeer gave - as with any skyline query - can be solved with
just pure SQL:
select * from books b where not exists(
select * from books b2 where
b2.rating = b.rating and b2.price = b.price and
(b2.rating b.rating or b2.price b.price)
);
book_name | rating | price
Tom,
My questions about whether to adopt it have more to do with
cost/benefit. I haven't seen the patch, but it sounds like it will be
large and messy; and it's for a feature that nobody ever heard of before,
let alone one that the community has developed a consensus it wants.
I'm not
Josh Berkus wrote:
Now, I don't know if this Skyline patch is our answer for approximate queries.
Maybe I should pester Meredith about getting QBE free of its IP issues; it
certainly looked more flexible than Skyline. In either case, the code
probably needs a complete refactor.
But I
On Wed, 7 Mar 2007, Josh Berkus wrote:
Approximate queries is something with DSS users *want*. Jim Grey addressed
this in his ACM editiorial on the databases of the future. It's something
that *I* want, and if the Greenplum people aren't speaking up here, it's
because they're not paying
on ma treo
-Original Message-
From: Gavin Sherry [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 07, 2007 05:44 PM Eastern Standard Time
To: Josh Berkus
Cc: Tom Lane; pgsql-hackers@postgresql.org; Alvaro Herrera; Chris Browne
Subject:Re: [HACKERS] PostgreSQL - 'SKYLINE
Tom Lane wrote:
Josh Berkus josh@agliodbs.com writes:
I think if the code is good enough, and we can avoid horrible non-standard
syntax extensions, they should go in. We have to defend our title as most
advanced database and having stuff like Skyline first (before DB2 or MS)
goes a long way
Shane Ambler [EMAIL PROTECTED] writes:
Tom Lane wrote:
Well, whether it's horrible or not is in the eye of the beholder, but
this is certainly a non-standard syntax extension.
Being non-standard should not be the only reason to reject a worthwhile
feature.
No, but being non-standard is
On Mon, Mar 05, 2007 at 09:04:46PM -0600, Jim Nasby wrote:
FWIW, this sounds like a subset of the Query By Example stuff that
someone is working on. I don't have a URL handy since I'm on a plane,
but I think google can find it.
It's now called ObelisQ http://pgfoundry.org/projects/qbe
[EMAIL PROTECTED] (Jim Nasby) writes:
FWIW, this sounds like a subset of the Query By Example stuff that
someone is working on. I don't have a URL handy since I'm on a plane,
but I think google can find it.
The pgFoundry project is here...
http://pgfoundry.org/projects/qbe
And yes, indeed,
And yes, indeed, this sounds quite a lot like what Meredith Patterson
presented at the Toronto conference.
This would be good to have, though, since Meredith's work has some problematic
IP encumbrances.
Question, though: is the SKYLINE syntax part of a standard anywhere?
--
Josh Berkus
Josh Berkus josh@agliodbs.com writes:
Question, though: is the SKYLINE syntax part of a standard anywhere?
There's certainly not anything like that in SQL2003.
I'm also kind of wondering if the main use-cases couldn't be met with
suitable multi-input custom aggregates, which is something we
Tom,
I'm also kind of wondering if the main use-cases couldn't be met with
suitable multi-input custom aggregates, which is something we already
have as of 8.2.
Actually, given that skyline of is *only* for aggregate sorting (as far as I
can tell) it doesn't present the complications which
Josh Berkus wrote:
Tom,
I'm also kind of wondering if the main use-cases couldn't be met with
suitable multi-input custom aggregates, which is something we already
have as of 8.2.
Actually, given that skyline of is *only* for aggregate sorting (as far as
I
can tell) it doesn't
On Tue, 6 Mar 2007, Alvaro Herrera wrote:
Also, keep in mind that there were plenty of changes in the executor.
This stuff is not likely to be very easy to implement efficiently using
our extant executor machinery; note that Ranbeer mentioned
implementation of block nested loop and other
FWIW, this sounds like a subset of the Query By Example stuff that
someone is working on. I don't have a URL handy since I'm on a plane,
but I think google can find it.
On Mar 3, 2007, at 8:12 AM, ranbeer makin wrote:
Here is a description of what the SKYLINE operator is:
---
Suppose you
We at International Institute of Information Technology (IIIT) Hyderabad,
India, have extended the Postgres database
system with the skyline operation. For this work, we were guided by our
Prof. Kamalakar Karlapalem
(http://www.iiit.ac.in/~kamal/).
We have extended SQL 'SELECT' clause by an
On Sat, Mar 03, 2007 at 07:02:41PM +0530, ranbeer makin wrote:
We at International Institute of Information Technology (IIIT) Hyderabad,
India, have extended the Postgres database
system with the skyline operation. For this work, we were guided by our
Prof. Kamalakar Karlapalem
Martijn van Oosterhout wrote:
Well, that kind of depends. I have no idea what Skyline means so
telling us what it is would be a good start
Also, showing us the diffs (maybe on a web site) would give us an idea
of how intrusive it would be.
But I agree with Martijn - the first thing
Here is a description of what the SKYLINE operator is:
---
Suppose you wish to purchase books and you are looking for books with high
rating and low price. However, both the criteria of selecting books are
complementary since books of higher rating are generally more expensive. For
finding such
ranbeer makin wrote:
We at International Institute of Information Technology (IIIT) Hyderabad,
India, have extended the Postgres database
system with the skyline operation. For this work, we were guided by our
Prof. Kamalakar Karlapalem
(http://www.iiit.ac.in/~kamal/).
We have extended SQL
You most probably want to look at porting your changes to the latest
postgresql release as well.
I believe many people would be interested, but to get the feature
accepted we would need a patch against -head as that is the latest
version of PostgreSQL under development.
You can see more
27 matches
Mail list logo
