Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 508089FA173 for ; Sat, 16 Dec 2006 08:12:12 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 35704-02 for ; Sat, 16 Dec 2006 08:11:58 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 4E4A79F9F47 for ; Sat, 16 Dec 2006 08:12:02 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from swarthymail-a3.dreamhost.com (mailbigip.dreamhost.com [208.97.132.5]) by svr4.postgresql.org (Postfix) with ESMTP id 792F45AF8A9 for ; Sat, 16 Dec 2006 12:12:01 +0000 (GMT) Received: from [192.168.2.44] (u25-56.dsl.vianetworks.de [212.168.164.56]) by swarthymail-a3.dreamhost.com (Postfix) with ESMTP id 731A27F01B; Sat, 16 Dec 2006 04:11:59 -0800 (PST) Subject: Re: Embedding postgresql in my application From: Murray Cumming To: "Jeroen T. Vermeulen" Cc: pgsql-interfaces In-Reply-To: <6147.125.24.243.222.1166270151.squirrel@webmail.xs4all.nl> References: <1166225144.12609.2.camel@localhost.localdomain> <20058.125.24.243.222.1166249768.squirrel@webmail.xs4all.nl> <1166267606.5923.11.camel@localhost.localdomain> <9856.125.24.243.222.1166268615.squirrel@webmail.xs4all.nl> <1166269673.5923.17.camel@localhost.localdomain> <6147.125.24.243.222.1166270151.squirrel@webmail.xs4all.nl> Content-Type: text/plain Date: Sat, 16 Dec 2006 13:11:56 +0100 Message-Id: <1166271116.5923.27.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.018 tagged_above=0 required=5 tests=AWL, BAYES_50 X-Spam-Level: X-Archive-Number: 200612/16 X-Sequence-Number: 6350 On Sat, 2006-12-16 at 18:55 +0700, Jeroen T. Vermeulen wrote: > Ah--I had not understood that you wanted to access the database > remotely. > But in that case, in what sense would the database be "embedded" in > your > application!? It's not the best word, I guess. I just wanted to express that I'd be using Postgres only for my application, without using the system's regular Postgres installation/configuration. My aims are: - The user doesn't need to be clever or patient enough to install and configure postgres to support TCP/IP connections. This is unnecessarily difficult on most distros: http://www.glom.org/wiki/index.php?title=Initial_Postgres_Configuration The file-opening experience would then be the same as when opening a FileMaker or Access file. - I can make choices about the default connection policy without interfering with the connection policy wanted by other applications that use postgres, or with the default policy wanted (understandably) by the disto packager. - The Glom "system" (the database plus the UI description, etc) can be copied and started on a different computer easily. - The first user to open a Glom file becomes the server for that .glom file, and other users connect to that first client (the server). This is how FileMaker works. A central server, for better performance, is then an extra choice that can be used when wanted. -- Murray Cumming murrayc@murrayc.com www.murrayc.com www.openismus.com