-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 pain
[EMAIL PROTECTED] (Ned Lilly) wrote in message news:[EMAIL PROTECTED]...
Jonathan,
This is exactly how my company has built a very robust ERP application. See
www.openmfg.com.
Hi Mr. Lilly:
I not sure who to address this question to at your company.
I'm a valued added reseller who
Jonathan M. Gardner wrote:
Thoughts? Comments? Hasn't Oracle done something like this?
Probably this is more suited to -general?
I haven't done anything near this. I wonder how much more painful it is
to debug the application, put it under version control, etc. Personally,
I can't stand
On Thu, 2004-08-05 at 22:27, Jonathan M. Gardner wrote:
A few nights ago, I implemented some of my application logic in PostgreSQL
via PL/PythonU. I was simply amazed at what I was able to do. My question
becomes: Why not get rid of the middle layer and move it into the databse
entirely?
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 pain in the ass for many types of
codes. I might have missed something in the intervening years, but I
Although
On Fri, 2004-08-06 at 10:53, Joshua D. Drake wrote:
Although the gap still exists within the environment itself, one
significant advantage with PostgreSQL is you can use a more native (to
the programmer anyway) language to generate your logic.
With PostgreSQL alone you can use plPerl,
-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
