Joshua D. Drake wrote:
I am pulling this way out of the back of my head, and Peter might be
a better one to ask but I seem to recall that you can set the closing
bracket requirement in the stylesheet itself.
That is incorrect.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
Warren Turkal wrote:
XML should require the closing tag.
But this is not XML.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
Warren Turkal wrote:
On Friday 02 March 2007 16:46, Joshua D. Drake wrote:
I am pulling this way out of the back of my head, and Peter might be a
better one to ask but I seem to recall that you can set the closing
bracket requirement in the stylesheet itself.
XML should require the closing
On Fri, Mar 02, 2007 at 06:42:14PM -0600, Andrew Dunstan wrote:
I'm still not happy about the idea of doing this for every relation
(and doing it for sequences and indexes would be the height of
wastefulness). How about we only do it for composite types?
I'm not happy about that. I agree
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:
On Fri, Mar 02, 2007 at 06:42:14PM -0600, Andrew Dunstan wrote:
I'm still not happy about the idea of doing this for every relation
(and doing it for sequences and indexes would be the height of
wastefulness). How about we only do it for composite types?
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
Peter Eisentraut wrote:
Bruce Momjian wrote:
I have added to the developer's FAQ that we don't want
non-BSD-compatible licensed patches:
How frequently is this actually a problem?
I don't think it is common. I didn't add that part, so if you also
think it is rare, I will remove that
Peter Eisentraut wrote:
Bruce Momjian wrote:
I have added to the developer's FAQ that we don't want
non-BSD-compatible licensed patches:
How frequently is this actually a problem?
Every single time someone submits a patch with no license but with a big
legal disclaimer in their signature.
Joshua D. Drake wrote:
Peter Eisentraut wrote:
Bruce Momjian wrote:
I have added to the developer's FAQ that we don't want
non-BSD-compatible licensed patches:
How frequently is this actually a problem?
Every single time someone submits a patch with no license but with a big
legal
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
Bruce Momjian wrote:
Peter Eisentraut wrote:
Bruce Momjian wrote:
I have added to the developer's FAQ that we don't want
non-BSD-compatible licensed patches:
How frequently is this actually a problem?
I don't think it is common. I didn't add that part, so if you also
think it is rare, I
Bruce Momjian wrote:
Joshua D. Drake wrote:
Peter Eisentraut wrote:
Bruce Momjian wrote:
I have added to the developer's FAQ that we don't want
non-BSD-compatible licensed patches:
How frequently is this actually a problem?
Every single time someone submits a patch with no license but with
Joshua D. Drake wrote:
Bruce Momjian wrote:
Joshua D. Drake wrote:
Peter Eisentraut wrote:
Bruce Momjian wrote:
I have added to the developer's FAQ that we don't want
non-BSD-compatible licensed patches:
How frequently is this actually a problem?
Every single time someone submits a
Bruce Momjian wrote:
Joshua D. Drake wrote:
Bruce Momjian wrote:
Joshua D. Drake wrote:
Peter Eisentraut wrote:
Bruce Momjian wrote:
I have added to the developer's FAQ that we don't want
non-BSD-compatible licensed patches:
How frequently is this actually a problem?
Every single time
On Sat, Mar 03, 2007 at 09:06:11AM -0500, Andrew Dunstan wrote:
Martijn van Oosterhout wrote:
On Fri, Mar 02, 2007 at 06:42:14PM -0600, Andrew Dunstan wrote:
I'm still not happy about the idea of doing this for every relation
(and doing it for sequences and indexes would be the height
David Fetter [EMAIL PROTECTED] writes:
2. Make a command: CREATE TYPE ARRAY OF foo;
The latter has the benefit of not restricting it to an arbitrary choice
of types, you could accept both domains and composite types here.
I'm thinking that DOMAINs over simple types should just
Joshua D. Drake wrote:
Oh, I just meant that when *new* people signup they are made aware of
the predetermined policy based on joining the group. That way there is
zero confusion because when they went to the website and signed up, we
made the point of the BSD license, and when they were
Alvaro Herrera wrote:
Joshua D. Drake wrote:
Oh, I just meant that when *new* people signup they are made aware of
the predetermined policy based on joining the group. That way there is
zero confusion because when they went to the website and signed up, we
made the point of the BSD license,
Hello,
I am trying to create a new index which is multidimensional (based on
R-Tree) which can be used for data warehosuing. I have read the Developers'
manual about adding new indexes, and now I want to start coding the new
index.
My first step is to create the skeleton files, but I cannot
I have applied a modified version of this patch, attached. I trimmed
down the description of log_lock_waits to be more concise, and moved the
idea of using this to tune deadlock_timeout to the deadlock_timeout
section of the manual.
Alan Gatt wrote:
Hello,
I am trying to create a new index which is multidimensional (based on
R-Tree) which can be used for data warehosuing. I have read the Developers'
manual about adding new indexes, and now I want to start coding the new
index.
My first step is to create the skeleton
FYI, I see the following warnings compiling CVS HEAD:
src/pl/plpython/plpython.c:2006: warning: initialization from
incompatible pointer type
src/pl/plpython/plpython.c:2008: warning: 'intargfunc' is deprecated
src/pl/plpython/plpython.c:2008: warning: initialization from
incompatible pointer
Neil Conway wrote:
FYI, I see the following warnings compiling CVS HEAD:
src/pl/plpython/plpython.c:2006: warning: initialization from
incompatible pointer type
src/pl/plpython/plpython.c:2008: warning: 'intargfunc' is deprecated
src/pl/plpython/plpython.c:2008: warning: initialization from
src/pl/plpython/plpython.c:2010: warning: 'intintargfunc' is deprecated
src/pl/plpython/plpython.c:2010: warning: initialization from
incompatible pointer type
src/pl/plpython/plpython.c:2011: warning: initialization from
incompatible pointer type
src/pl/plpython/plpython.c:2012: warning:
On Sat, 2007-03-03 at 11:21 -0800, Joshua D. Drake wrote:
There is no Ubuntu Fiesty... yet ;) you are compile -head with -head...
sounds like a snafu to begin with
No, it just looks like a Python API 2.5 change to me. I'd look into it
myself, but I don't have the free cycles at the moment.
On Sat, Mar 03, 2007 at 07:38:15PM +0100, Alan Gatt wrote:
Hello,
I am trying to create a new index which is multidimensional (based on
R-Tree) which can be used for data warehosuing. I have read the Developers'
manual about adding new indexes, and now I want to start coding the new
index.
Patch applied. Thanks.
---
Florian G. Pflug wrote:
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
I think you should increase pg_control version.
And the WAL page-header version, since this also
Patch applied. Thanks.
---
Florian G. Pflug wrote:
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
I think you should increase pg_control version.
And the WAL page-header version, since this also
Alan Gatt escribió:
Hello,
I am trying to create a new index which is multidimensional (based on
R-Tree) which can be used for data warehosuing. I have read the Developers'
manual about adding new indexes, and now I want to start coding the new
index.
Have you considered coding it using
On Saturday 03 March 2007 13:02, Joshua D. Drake wrote:
Alvaro Herrera wrote:
Joshua D. Drake wrote:
Oh, I just meant that when *new* people signup they are made aware of
the predetermined policy based on joining the group. That way there is
zero confusion because when they went to the
David Fetter wrote:
Per your earlier suggestion in IRC, I'm picturing a polymorphic
function like
pg_catalog.array_for(typepoid OID)
pg_catalog.array_for(typename NAME)
pg_catalog.array_for(typenamespace NAME, typename NAME)
I don't see a good reason to allow putting array types in a different
On Monday 26 February 2007 19:27, A.M. wrote:
On Feb 26, 2007, at 18:58 , Simon Riggs wrote:
On Mon, 2007-02-26 at 23:25 +, Richard Huxton wrote:
Simon Riggs wrote:
Proposal: Implement a new option for COMMIT, for enhancing
performance,
providing a MySQL-like trade-off between
Robert Treat wrote:
On Saturday 03 March 2007 13:02, Joshua D. Drake wrote:
Alvaro Herrera wrote:
Joshua D. Drake wrote:
Oh, I just meant that when *new* people signup they are made aware of
the predetermined policy based on joining the group. That way there is
zero confusion because when
Ok, so I am using GCC 3.2 as a compiler, and the following is the error
message:
make[4]: Entering directory
`/c/dev/postgres/pgsql_tip/src/backend/access/mdim'
gcc -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Winline
-Wdeclaration-after-statement -Wendif-labels -fno-strict-aliasing -g
38 matches
Mail list logo
