Skip site navigation (1) Skip section navigation (2)

Re: [INTERFACES] Re: [HACKERS] pgbash-1.1.1 release

From: "Gene Selkov Jr(dot)" <selkovjr(at)xnet(dot)com>
To: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, pgsql-interfaces(at)postgreSQL(dot)org
Subject: Re: [INTERFACES] Re: [HACKERS] pgbash-1.1.1 release
Date: 1999-10-02 04:51:14
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
> I have to connect to any database to issue
> exec_sql -l database

A database name is required to connect (by libpq? protocol?).  This
can be cured by using template1 as a default. However, the issue
naturally develops into a more serious concern: are we going to have
inter-database queries in any plausible future?



The idea of adding a database interface to sh, although I can
immediately see its usefulness, srikes me funny. We are apparently
looking to have an elisp interface soon (thanks to Eric Marsden);
sooner or later, one will be finding the SQL code stashed everywhere
throughout the system. Would it then be wrong to expect the whole
backend embedded into the unix kernel? That would definitely swallow a
share of IBM's server market ;-> Now think about this: after wrapping
it up into the kernel, what will prevent you from building a Prolog on
top of it? Next thing that comes to mind would be a neural network
interface to the postgres-enabled prolog-backtracking unix kernel. 

The chances of winnning a Rube Godberg contest are already high and
rising ...

pgsql-interfaces by date

Next:From: Gene Selkov, Jr.Date: 1999-10-02 05:02:43
Subject: Re: [INTERFACES] Re: [HACKERS] pgbash-1.1.1 release
Previous:From: SAKAIDADate: 1999-10-02 04:00:49
Subject: Re: [HACKERS] pgbash-1.1.1 release

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group