Re: oracle : The lowdown

2000-01-20 Thread Perrin Harkins
Perrin Harkins wrote: Greg Stark wrote: For example, it makes it very hard to mix any kind of long running query with OLTP transactions against the same data, since rollback data accumulates very quickly. I would give some appendage for a while to tell Oracle to just use the most recent

Re: oracle : The lowdown

2000-01-20 Thread Ed Phillips
For those of you tired of this thread please excuse me, but here is MySQL's current position statement on and discussion about transactions: Disclaimer: I just helped Monty write this partly in response to some of the fruitful, to me, discussion on this list. I know this is not crucial to

Re: oracle : The lowdown

2000-01-19 Thread Greg Stark
Matt Sergeant [EMAIL PROTECTED] writes: Depends what the business is. If it is a serious business looking for VC I would actually suspect the inverse is true: MySQL is underkill (I think I just made that word up) due to its lack of transactions and other advanced features (yes, these things

Re: oracle : The lowdown

2000-01-14 Thread Keith G. Murphy
David Harris wrote: Jeff Warner wrote: We were a mySQL shop. We replaced mySQL with Oracle8i/mod_perl and and Apache::DBI. Works great, once it is all setup. Our overall processing is faster with Oracle too. The lack of transactions and views put an immediate end of mySQL

Re: oracle : The lowdown

2000-01-12 Thread Matt Sergeant
On Tue, 11 Jan 2000, Michael wrote: On Tue, 11 Jan 2000, John Armstrong wrote: Hello all- I just got the word from down high that VC's will freak out if they see we are using mysql and now we are looking at an Oracle solution. The product is a mid level mod perl

Re: oracle : The lowdown

2000-01-12 Thread Joshua Chamas
Matt Sergeant wrote: On Tue, 11 Jan 2000, Joshua Chamas wrote: BTW, I have also evaled Sybase, Informix, DB2, SQLServer 6.5, Solid, and found Oracle to be the best of all those, but if you don't need transactions, go with MySQL... Do you mind sharing with me (if not the list) why

oracle : The lowdown

2000-01-11 Thread John Armstrong
Hello all- I just got the word from down high that VC's will freak out if they see we are using mysql and now we are looking at an Oracle solution. The product is a mid level mod perl application that will receive ~500,000 hits a day. I want to engineer it to withstand up to

Re: oracle : The lowdown

2000-01-11 Thread Jeff Warner
Title: Re: oracle : The lowdown We were a mySQL shop. We replaced mySQL with Oracle8i/mod_perl and and Apache::DBI. Works great, once it is all setup. Our overall processing is faster with Oracle too. The lack of transactions and views put an immediate end of mySQL once we got

Re: oracle : The lowdown

2000-01-11 Thread Matt Sergeant
On Tue, 11 Jan 2000, John Armstrong wrote: Hello all- I just got the word from down high that VC's will freak out if they see we are using mysql and now we are looking at an Oracle solution. The product is a mid level mod perl application that will receive ~500,000 hits a

Re: oracle : The lowdown

2000-01-11 Thread Mark Wagner
Hello all- I just got the word from down high that VC's will freak out if they see we are using mysql and now we are looking at an Oracle solution. (Um, are these VC's in a position to make an informed decision about which RDBMS to use? What happens when they say "use foo" when foo

RE: oracle : The lowdown

2000-01-11 Thread David Harris
Jeff Warner wrote: We were a mySQL shop. We replaced mySQL with Oracle8i/mod_perl and and Apache::DBI. Works great, once it is all setup. Our overall processing is faster with Oracle too. The lack of transactions and views put an immediate end of mySQL once we got into the details

Re: oracle : The lowdown

2000-01-11 Thread Michael
On Tue, 11 Jan 2000, John Armstrong wrote: Hello all- I just got the word from down high that VC's will freak out if they see we are using mysql and now we are looking at an Oracle solution. The product is a mid level mod perl application that will receive ~500,000 hits

RE: oracle : The lowdown

2000-01-11 Thread John Armstrong
On this thread, I am seeing a lot of things in the archives hinting at issues and problems with Apache::Session ( DBI usage ) and high end DB's like Oracle and SyBase. What sort of success is anyone seeing using Oracle/SyBase with Apache::Session. Apache::Session in a DBI context is crucial

RE: oracle : The lowdown

2000-01-11 Thread Ian Mahuron
From past experiences I'll tell you that PostgreSQL is *dog slow*! We had a search engine with about 10,000 entries in it that was being run on MySQL, moved it to PostgreSQL and *bam*.. even with proper indexing limiting queries, it took 2-5 seconds to execute a simple query (server was load

Re: oracle : The lowdown

2000-01-11 Thread Jeffrey W. Baker
David Harris wrote: Jeff Warner wrote: We were a mySQL shop. We replaced mySQL with Oracle8i/mod_perl and and Apache::DBI. Works great, once it is all setup. Our overall processing is faster with Oracle too. The lack of transactions and views put an immediate end of mySQL

Re: oracle : The lowdown

2000-01-11 Thread Jeff Groves
Take a look at Frontbase www.frontbase.com From what I can see, it does everything that Oracle or Sybase can do and is much more reasonable in price. They're a small company and the support has been excellent. We've outgrown MySQL and are planning to use Frontbase to replace it. At 01:08 PM

Re: oracle : The lowdown

2000-01-11 Thread Jeffrey W. Baker
John Armstrong wrote: On this thread, I am seeing a lot of things in the archives hinting at issues and problems with Apache::Session ( DBI usage ) and high end DB's like Oracle and SyBase. What sort of success is anyone seeing using Oracle/SyBase with Apache::Session. Apache::Session in

Re: oracle : The lowdown

2000-01-11 Thread Bill
David Harris wrote: What about PostgreSQL (www.postgresql.org)? It looks like it has transaction management (commit, rollback) with the whole concurrency control thing. I don't know if has views. I've got a small project that I am figuring on using PostgreSQL for, so I'm curious to hear

Re: oracle : The lowdown

2000-01-11 Thread Tim Bunce
On Tue, Jan 11, 2000 at 01:20:21PM -0800, Jeffrey W. Baker wrote: Unfortunately, Oracle support is an ongoing criminal enterprise. Unless you have the most expensive of all of their support contracts, and a former Oracle VP on your staff, you will not get any support period. If you

Re: oracle : The lowdown

2000-01-11 Thread Joshua Chamas
John Armstrong wrote: Hello all- I just got the word from down high that VC's will freak out if they see we are using mysql and now we are looking at an Oracle solution. The product is a mid level mod perl application that will receive ~500,000 hits a day. I want to

RE: oracle : The lowdown

2000-01-11 Thread Ian Mahuron
Joshua but if you don't need transactions, go with MySQL... Or sub-selects.. I can't live without sub-selects!

RE: oracle : The lowdown

2000-01-11 Thread Autarch
On Tue, 11 Jan 2000, David Harris wrote: This link was just posted to the IMP list a couple min ago: "Low-Cost Unix Database Differences" http://www.toodarkpark.org/computers/dbs.html Stas, this might be a good link to drop somewhere in the guide. This is probably getting pretty

Re: oracle : The lowdown

2000-01-11 Thread G.W. Haywood
Hi all, On Tue, Jan 11, 2000 at 01:20:21PM -0800, Jeffrey W. Baker wrote: Unfortunately, Oracle support is an ongoing criminal enterprise. Unless you have the most expensive of all of their support contracts, and a former Oracle VP on your staff, you will not get any support period. If you

Re: oracle : The lowdown

2000-01-11 Thread Tim Bunce
On Tue, Jan 11, 2000 at 02:50:52PM -0800, Ian Mahuron wrote: Joshua but if you don't need transactions, go with MySQL... Or sub-selects.. I can't live without sub-selects! Sub-selects are high on the to-do list, and the rate that they're advancing MySQL they'll be available quite soonish.