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
<[EMAIL PROTECTED]> wrote:
> > completely proprietary front end written in python. Any help finding
> > useful
>
> What does "a completely proprietary front-end in python" means ?
>
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
