Re: [GENERAL] To Postgres or not

2005-07-14 Thread Gregory Youngblood
On Jul 13, 2005, at 9:57 PM, Alvaro Herrera wrote:On Thu, Jul 14, 2005 at 02:46:01PM +1000, Neil Conway wrote: Vivek Khera wrote: The first sentence rules out MySQL, so the second sentence should  read "So that leaves Postgres".  Your problem is solved ;-)(If you are accustomed to Oracle, you are p

Re: [GENERAL] To Postgres or not

2005-07-14 Thread Ted Slate
To everyone, Thanks very much for your replies, and if these responses are any indication of Postgres quality then I'd be in good hands. Ted _ Don’t just search. Find. Check out the new MSN Search! http://search.msn.click-url.co

Re: [GENERAL] To Postgres or not

2005-07-14 Thread Scott Marlowe
On Wed, 2005-07-13 at 23:57, Alvaro Herrera wrote: > On Thu, Jul 14, 2005 at 02:46:01PM +1000, Neil Conway wrote: > > Vivek Khera wrote: > > >The first sentence rules out MySQL, so the second sentence should read > > >"So that leaves Postgres". Your problem is solved ;-) > > > > > >(If you are a

Re: [GENERAL] To Postgres or not

2005-07-14 Thread Magnus Hagander
> > >The first sentence rules out MySQL, so the second sentence should > > >read "So that leaves Postgres". Your problem is solved ;-) > > > > > >(If you are accustomed to Oracle, you are probably > expecting an ACID > > >database, which rules out MySQL too). > > > > Does MySQL with InnoDB no

Re: [GENERAL] To Postgres or not

2005-07-14 Thread Tino Wildenhain
Am Donnerstag, den 14.07.2005, 00:57 -0400 schrieb Alvaro Herrera: > On Thu, Jul 14, 2005 at 02:46:01PM +1000, Neil Conway wrote: > > Vivek Khera wrote: > > >The first sentence rules out MySQL, so the second sentence should read > > >"So that leaves Postgres". Your problem is solved ;-) > > > >

Re: [GENERAL] To Postgres or not

2005-07-14 Thread Randal L. Schwartz
> "Neil" == Neil Conway <[EMAIL PROTECTED]> writes: Neil> Does MySQL with InnoDB not qualify as an ACID-compliant database? Not when you can store a value that is larger than allowed, and it is silently truncated to be within range. no *I* integrity there. That's regardless of InnoDB or not

Re: [GENERAL] To Postgres or not

2005-07-13 Thread Roman Neuhauser
# [EMAIL PROTECTED] / 2005-07-14 00:57:57 -0400: > On Thu, Jul 14, 2005 at 02:46:01PM +1000, Neil Conway wrote: > > Vivek Khera wrote: > > >The first sentence rules out MySQL, so the second sentence should read > > >"So that leaves Postgres". Your problem is solved ;-) > > > > > >(If you are acc

Re: [GENERAL] To Postgres or not

2005-07-13 Thread Alvaro Herrera
On Thu, Jul 14, 2005 at 02:46:01PM +1000, Neil Conway wrote: > Vivek Khera wrote: > >The first sentence rules out MySQL, so the second sentence should read > >"So that leaves Postgres". Your problem is solved ;-) > > > >(If you are accustomed to Oracle, you are probably expecting an ACID > >da

Re: [GENERAL] To Postgres or not

2005-07-13 Thread Neil Conway
Vivek Khera wrote: The first sentence rules out MySQL, so the second sentence should read "So that leaves Postgres". Your problem is solved ;-) (If you are accustomed to Oracle, you are probably expecting an ACID database, which rules out MySQL too). Does MySQL with InnoDB not qualify as

Re: [GENERAL] To Postgres or not

2005-07-13 Thread Jim C. Nasby
On Wed, Jul 13, 2005 at 04:24:53PM -0400, Vivek Khera wrote: > > On Jul 12, 2005, at 1:16 PM, Ted Slate wrote: > > >If I stick with a true RDBMS then Codebase is out. So that leaves > >Postgres and MySQL. > > The first sentence rules out MySQL, so the second sentence should > read "So that

Re: [GENERAL] To Postgres or not

2005-07-13 Thread Bob
Even though PostgreSQL is more like an Oracle which is a good thing. It's like Oracle in function not in cost and adminstration. PostgreSQL not only fits into the enterprice really well it also fits in the mom and pop shops(dentist office,corner store, you name it that may not have any IT folks.  S

Re: [GENERAL] To Postgres or not

2005-07-13 Thread David Fetter
On Tue, Jul 12, 2005 at 05:16:44PM +, Ted Slate wrote: > Hello Everyone, > > I considering moving a product to Solaris/Linux and trying to find a > good DB. Oracle is out due to cost so as far as i know the only > reasonable alternatives are Postgres or Codebase or MySQL. Does > anyone here

Re: [GENERAL] To Postgres or not

2005-07-13 Thread Vivek Khera
On Jul 12, 2005, at 1:16 PM, Ted Slate wrote: If I stick with a true RDBMS then Codebase is out. So that leaves Postgres and MySQL. The first sentence rules out MySQL, so the second sentence should read "So that leaves Postgres". Your problem is solved ;-) (If you are accustomed to Ora

Re: [GENERAL] To Postgres or not

2005-07-13 Thread Tadej Kanizar
: pgsql-general@postgresql.org Subject: [GENERAL] To Postgres or not Hello Everyone, I considering moving a product to Solaris/Linux and trying to find a good DB. Oracle is out due to cost so as far as i know the only reasonable alternatives are Postgres or Codebase or MySQL. Does anyone here have

Re: [GENERAL] To Postgres or not

2005-07-13 Thread Michael Schmidt
There are a number of good, objective, and informative comparisons available on the Internet, such as http://www.databasejournal.com/sqletc/article.php/3486596.  You can Google something like "Postgresql mysql firebird comparison" to access these.  I am migrating an application from Paradox a

Re: [GENERAL] To Postgres or not

2005-07-13 Thread Tino Wildenhain
Am Dienstag, den 12.07.2005, 17:16 + schrieb Ted Slate: > Hello Everyone, > > I considering moving a product to Solaris/Linux and trying to find a good > DB. Oracle is out due to cost so as far as i know the only reasonable > alternatives are Postgres or Codebase or MySQL. Does anyone here

[GENERAL] To Postgres or not

2005-07-13 Thread Ted Slate
Hello Everyone, I considering moving a product to Solaris/Linux and trying to find a good DB. Oracle is out due to cost so as far as i know the only reasonable alternatives are Postgres or Codebase or MySQL. Does anyone here have any experience using Codebase or MySql? If I stick with a tru