Re: Triggers, Stored Procedures, PHP. was: Re: [GENERAL] PostgreSQL

2003-12-07 Thread Joshua D. Drake
You don't have to disagree with me, I can have arguments with myself over nothing. Some would call that insanity, I call it genius. Sincerely, Joshua D. Drake -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC - S/JDBC Postgresql support, programming, shared hosting and dedicated h

Re: Triggers, Stored Procedures, PHP. was: Re: [GENERAL] PostgreSQL

2003-12-02 Thread scott.marlowe
On Tue, 2 Dec 2003, Jan Wieck wrote: > scott.marlowe wrote: > > > On Mon, 1 Dec 2003, Jan Wieck wrote: > > > >> Jason Tesser wrote: > >> > >> > Quoted as gospel by various people: > >> >>> MySQL cannot even handle sub-queries yet. > >> > > >> >> BTW, is that really still true? I thought they

Re: Triggers, Stored Procedures, PHP. was: Re: [GENERAL] PostgreSQL

2003-12-02 Thread Jan Wieck
scott.marlowe wrote: On Mon, 1 Dec 2003, Jan Wieck wrote: Jason Tesser wrote: > Quoted as gospel by various people: >>> MySQL cannot even handle sub-queries yet. > >> BTW, is that really still true? I thought they had at least some >> support for subqueries by now. > > yes sub queries in 4.1

Re: Triggers, Stored Procedures, PHP. was: Re: [GENERAL] PostgreSQL

2003-12-01 Thread Jonathan Bartlett
> python that you can't do in PHP? Python is an immensely powerful language. It is essentially the successor to both LISP and Smalltalk. It has things like closures (well, not complete, but pretty close), generators, a huge OO library, easy-to-use exceptions (i.e. - in comparison to Java), and I

Re: Triggers, Stored Procedures, PHP. was: Re: [GENERAL] PostgreSQL

2003-12-01 Thread Randal L. Schwartz
> "Jay" == Jay O'Connor <[EMAIL PROTECTED]> writes: Jay> Python also reads more obviously, in that it doesn't have a lot of Jay> 'default context' ($_) and 'scalar context versus array context' and Jay> cute shortcuts and stuff floating around, which makes it easier to Jay> read, and more impo

Re: Triggers, Stored Procedures, PHP. was: Re: [GENERAL] PostgreSQL

2003-12-01 Thread Alvaro Herrera
On Mon, Dec 01, 2003 at 05:18:17PM -0700, Jay O'Connor wrote: > Personally, I would never use Perl for anything over about one hundred > lines and about one developer if I had any say in the matter. Takeing > Perl and mixing Presentation (HTML) with Business Logic (embedded > scripts) wihich s

Re: Triggers, Stored Procedures, PHP. was: Re: [GENERAL] PostgreSQL

2003-12-01 Thread Jay O'Connor
> >If you need more power IMO Python is the way to go. > I am not that familiar with pything, not to get off topic here but what you >can do in python that you can't do in PHP? Well if they are both Turing complete, arguably not much :) It's not the 'what' it's the 'how' I'm equating Perl with

Re: Triggers, Stored Procedures, PHP. was: Re: [GENERAL] PostgreSQL Advocacy, Thoughts and Comments

2003-12-01 Thread Rick Gigger
Note: I am a php developer and I love it, but... >In dealing with web applications and frontends to database or >even just a dynamic web site PHP has every bit the power and ability that >Java does and the development time is way down. Uh, how about threads. I know that you don't need them much

Re: Triggers, Stored Procedures, PHP. was: Re: [GENERAL] PostgreSQL Advocacy, Thoughts and Comments

2003-12-01 Thread Rick Gigger
aturday, November 29, 2003 10:01 AM Subject: Re: Triggers, Stored Procedures, PHP. was: Re: [GENERAL] PostgreSQL Advocacy, Thoughts and Comments > "Rod K" <[EMAIL PROTECTED]> writes: > > Paul Thomas wrote: > >> Much of the populatity of MySQL seems to stem from PHPs

Re: Triggers, Stored Procedures, PHP. was: Re: [GENERAL] PostgreSQL

2003-12-01 Thread scott.marlowe
On Mon, 1 Dec 2003, Jan Wieck wrote: > Jason Tesser wrote: > > > Quoted as gospel by various people: > >>> MySQL cannot even handle sub-queries yet. > > > >> BTW, is that really still true? I thought they had at least some > >> support for subqueries by now. > > > > yes sub queries in 4.1 whic

Re: Triggers, Stored Procedures, PHP. was: Re: [GENERAL] PostgreSQL Advocacy, Thoughts and Comments

2003-11-30 Thread Paul Thomas
On 29/11/2003 16:24 Jason Tesser wrote: [snip] A programmer that doesn't document stuff needs to find a new job :-) Agreed. So you're replaced him and inherited a documentation-free application. How many favours has he done you by squirrelling away section of business logic in the database? This

Re: Triggers, Stored Procedures, PHP. was: Re: [GENERAL] PostgreSQL Advocacy, Thoughts and Comments

2003-11-29 Thread Chris Travers
From: "Paul Thomas" <[EMAIL PROTECTED]>: > Stored procedures can be a 2-edged sword. They can lead to business logic > being scattered between the persistence layer and the business layer. > Thats not good for maintaining the application 3 years down the line. > Triggers can also cause maintenance

Re: Triggers, Stored Procedures, PHP. was: Re: [GENERAL] PostgreSQL Advocacy, Thoughts and Comments

2003-11-29 Thread Rod K
Paul Thomas wrote: > > > > On 28/11/2003 17:10 Jason Tesser wrote: > > [snip] > > > > MySQL cannot even handle > > sub-queries yet. I also use Python for standalone interfaces to > the data. > > > > Why should I not be able to use the same views and triggers etc > in there > > that I use for my

Re: Triggers, Stored Procedures, PHP. was: Re: [GENERAL] PostgreSQL

2003-11-29 Thread Jonathan Bartlett
> > Java has its own issues and I am not sure it is as far supiour as you > > are claming it is. But that is not for this dscussion. > > I'm not aware of any "issues" with Java (unless you mean Swing ;)). I know for one thing - Java's lack of support for returning tuples is hugely annoying. Jon

Triggers, Stored Procedures, PHP. was: Re: [GENERAL] PostgreSQL Advocacy, Thoughts and Comments

2003-11-29 Thread Paul Thomas
On 28/11/2003 17:10 Jason Tesser wrote: [snip] I completely disagree. I do a lot of programming with PHP and the features of Postgres come in handy. Let me give you an example of just some basic things. Triggers! Why should I have to write insert and update triggers in the logic (PHP) if I can