Hi Josh,
at first, thanks for all the interesting info given
Correct, AFAIK.
o extensions of PostgreSQL to support such a kind of usage have to be
expected to be expected to be rejected from integration to the code base
core -- i.e., if they are done, students have to be told «you can't
expec
(my last two posts seemingly did not reach the HACKERS forum, so please
let me resend the last one ;-) )
May I sum up?
o in the recent there are no efforts known to experiment with
reference types, methods, or rule inference on top of PostgreSQL --
advice that can be given mostly points to
May I sum up?
o in the recent there are no efforts known to experiment with
reference types, methods, or rule inference on top of PostgreSQL --
advice that can be given mostly points to the given documented functionality
o inside the PostgreSQL community, there is not many knowledge in
c
:
Nick Rudnick wrote:
here an inelegant example
Based on that example, you should be sure to look at the INHERITS
clause of CREATE TABLE:
http://www.postgresql.org/docs/current/interactive/sql-createtable.html
PostgreSQL has the "is a" structure built in. That may not get you
a
Hi Peter,
Another possibility is
foo->bar(baz)
This is in the SQL standard under, but
it requires the left side to be of a reference type, which is something
that we don't have.
I think this is the point where I stopped my efforts in the past -- I
guessed that a reference, in Postgre
is part of ANSi SQL 2003
http://savage.net.au/SQL/sql-2003-2.bnf.html#method%20specification%20designator
2011/2/1 Pavel Stehule:
2011/2/1 Robert Haas:
On Mon, Jan 31, 2011 at 5:09 PM, Nick Rudnick wrote:
Interesting... I remember that some years ago, I fiddled around with
functions
On 02/01/2011 03:36 AM, Robert Haas wrote:
On Mon, Jan 31, 2011 at 5:40 PM, Nick Rudnick wrote:
* In this regard it is of interest in how far there are principal efficiency
problems with the support of (deeply nested) object like structure by the
backend, or if the backend may be expected to
Hello Robert,
a good moment to clear things up:
* Of course, compliance with an ISO-SQL standard is of minimal
importance -- I just grabbed it from the docs.
* The same holds (in a somewhat weaker way) for Java -- I would even
prefer the more general notion type instead of OO, but I am askin
Interesting... I remember that some years ago, I fiddled around with
functions, operators etc. to allow a method like syntax -- but I ever
was worried this approach would have serious weaknesses -- are there any
principal hindrances to having methods, if no, can this be implemented
in a straigh
