-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 06 August 2004 10:00 am, J. Andrew Rogers wrote:
>
> The major disadvantage is that the development environment and tools
> for in-database languages aren't nearly as rich as your typical
> standalone environment, which makes programming a pa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Consider this. Most (well-written) applications are written in three
layers. The data abstraction layer provides a clean interface to the
underlying data so other people don't have to write SQL statements. The
GUI layer handles all the GUI events an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 03 August 2004 12:12 pm, Jonathan Gardner wrote:
> I'll look into how to actually implement this at home tonight.
Well, it's two nights later but I think I made some headway. I discovered
the joy that is backend/tcop/postgres.c. I discover
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Check out this gem.
=> CREATE TABLE t (i int);
=> CREATE OR REPLACE FUNCTION test() RETURNS VOID
LANGUAGE 'plpgsql' AS '
BEGIN
INSERT INTO t VALUES (1);
EXECUTE ''BEGIN'';
DELETE FROM t;
EXECUTE ''ROLLBACK'';
RETURN;
END
';
=> SELECT test(
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday 17 July 2004 9:55 am, Peter Eisentraut wrote:
> Jonathan M. Gardner wrote:
> > Should I submit documentation changes to the sgml files for nested
> > transcations? It will most likely be wrong, but maybe enough will be
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I know it's very early, but I think this is going to be important if you
want people (like me) who want to help test.
First off, the only reference to "nested transaction" I could find in the
documentation is a note that PostgreSQL does not have nes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 13 July 2004 7:33 pm, Christopher Kings-Lynne wrote:
>
> PHP's the same. Absolutely dreadful. They put all sorts of new
> features mixed in with security and bug fixes in their minor releases.
> The NUMBER OF TIMES I've upgraded PHP to fix
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 17 March 2004 5:54 pm, Christopher Kings-Lynne wrote:
> > I was thinking of writing a cron job to update the CVS tree and then
> > build the documentation (takes about 10 minutes on my computer). Then
> > I could push it to wherever you li
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 16 March 2004 5:56 pm, Bruce Momjian wrote:
> Jonathan Gardner wrote:
> > I'll start posting the documentation I am generating to my vanity
> > site (announcements later), but would this be something that the
> > postgresql.org main site wou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm not sure if my original reply made it through. Ignore the last one if
it did.
On Tuesday 24 February 2004 1:48 pm, Robert Treat wrote:
> On Tue, 2004-02-24 at 12:11, Richard Huxton wrote:
> > On Tuesday 24 February 2004 16:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've written a summary of my findings on implementing and using
materialized views in PostgreSQL. I've already deployed eagerly updating
materialized views on several views in a production environment for a
company called RedWeek: http://redweek.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've implemented a pretty simple Materialized Views scheme. It's not
terribly complicated, and it works quite well.
This is what I do.
0) Initialize the materialized view environment. This will allow the
system to track which tables and views are p
12 matches
Mail list logo
