mlw writes:
On the flip side, I am also working on a PostgreSQL SOAP interface,
where one does this:
http://somehost/postgresql?query=select * from table
And a SOAP compatible resultset is returned.
That looks quite similar to the planned XML functionality. While that
plan doesn't contain
Tom Lane wrote:
Kris Jurka [EMAIL PROTECTED] writes:
Is zeroing the pages the only / best option?
It's the only way to avoid a core dump when the system tries to process
the page. And no, I don't want to propagate the notion that this page
is broken beyond the buffer manager, so testing
I've found a web page that contains some examples of the use of the
features in the proposed SQL/XML standard (as implemented by Oracle).
This should give us some ideas about what to aim for.
http://otn.oracle.com/tech/xml/xmldb/htdocs/sql_xml_codeexamples.html
The third example converts a query
Hello,
I have the following problem. I have a database with different tables. This database is accessed from different users using different logins to access some of the tables.It's not a problem to limit the access of these users to certain tables.They can be included into a group and allowed
On Fri, Mar 28, 2003 at 11:13:28PM -0500, Tom Lane wrote:
The other thing that could be thought about here is when to freeze the
value of now(). Currently now() is frozen when BEGIN is received.
We could keep doing that, but it seems to me it would make more sense
to freeze now() when the
Why the Snapshot (SerializableSnapshot and QuerySnapshot) are malloc'ed
and not palloc'ed ? I wonder if I can switch to palloc to ease the
cleanup.
--
Alvaro Herrera (alvherre[a]dcc.uchile.cl)
La virtud es el justo medio entre dos defectos (Aristoteles)
---(end of
Hiroshi Inoue writes:
Must a SENSITIVE cursor see other applications' changes made
while the cursor is open ?
Yes. It is immaterial whether the change came from a different
application or the same one.
Nevertheless, the cursor sensitivity does not excuse you from observing
the transaction
Doug McNaught wrote:
Tom Lane [EMAIL PROTECTED] writes:
Accordingly, it's a bad idea to invent now('clock') and make it the
same function as the other flavors. We could get away with making
now('transaction') and now('statement') but the argument for this
was consistency, and that
I'm seeing this on CVS head:
make[4]: Entering directory
`/home/alvherre/CVS/pgsql/src/backend/access/common'
distcc -O2 -g -Wall -Wmissing-prototypes -Wmissing-declarations
-I../../../../src/include -c -o printtup.o printtup.c -MMD
In file included from ../../../../src/include/libpq/ip.h:8,
Bruce Momjian [EMAIL PROTECTED] writes:
Doug McNaught wrote:
Maybe clock_time() and statement_time(), with transaction_time() an
alias for now() (if that's seemed necessary)?
I could go with that ...
We already have CURRENT_TIMESTAMP. Would CLOCK_TIMESTAMP,
TRANSACTION_TIMESTAMP, and
10 matches
Mail list logo
