This is a discussion on Re: PYTHON, ODBC within the Pgsql General forums, part of the PostgreSQL category; --> ----- Forwarded message from Matthew Story <matthewstory@gmail.com> ----- Date: Sun, 9 Jan 2005 12:40:36 -0600 From: Matthew Story <matthewstory@gmail.com> ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| ----- Forwarded message from Matthew Story <matthewstory@gmail.com> ----- Date: Sun, 9 Jan 2005 12:40:36 -0600 From: Matthew Story <matthewstory@gmail.com> Reply-To: Matthew Story <matthewstory@gmail.com> Subject: Re: [GENERAL] PYTHON, ODBC To: Pierre-Frédéric Caillaud <lists@boutiquenumerique.com> we won't be using any tools aside from psycho pg, no gui application frameworks, ie we're not using zope, ruby on rails, etc. The front end will only work for this particular database. This has come about due to the complicated nature of the database, and inability of zope to do what we need, and the problems with overhead we've been experiencing with rails due to the size of the database. Hope this clears things up a bit. thanks, matt On Sun, 09 Jan 2005 14:56:57 +0100, Pierre-Frédéric Caillaud <lists@boutiquenumerique.com> wrote: > > completely proprietary front end written in python. Any help finding > > useful > > What does "a completely proprietary front-end in python" means ? > ----- End forwarded message ----- ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html |