Forum Moderators: open
Will MySQL include its most powerful storage engine into future updates?
I do not know why MySQL didn't go ahead and purchase InnoDB long time ago, knowing the importance of this storage engine. Hopefully, they will have a strong supplement to InnoDB which will allow them to continue on without it.
Oracle is a corporate giant and I believe this acquisition was intentional to cripple MySQL or have them at their mercy. I do not think Oracle goal is to have a GPL relatiionship with MySQL they will go forward with commercial licensing, I'm sure. I am also disappointed that InnoDB allowed this to happen, knowing the great influence it has had on the open-source community.
Oh! Well that's what you get when you have a kid in the basement coming up with bright ideas.
[edited by: jatar_k at 7:54 pm (utc) on Oct. 9, 2005]
[edit reason] to press release [/edit]
However, MySQL cannot include it in their commercial product without Oracle's permission, which almost certainly means they will drop it from the commercial version and open source version alike.
Exactly the right point -- InnoDB may be GPL, but that's the license not compatible with MySQL's commercial ambitions which are becoming more and more aggressive as of recent. By buying copyrights to InnoDB Oracle ensures that they can (when the time comes) undermine MySQL's ability to earn money by selling licenses. Very smart move on Oracle's behalf.
I love Postgre :-)
Not to be too nitpicky, but the correct nickname is "postgres" or "pgsql" or maybe "psql".
PostgreSQL is pronounced "post-gres'-que-el".
PostgreSQL was originally called Postgres, then Postgres95, and now PostgreSQL. I speak of the current software, without the 's'. The 's' has been deprecated along with waving my pinky when drinking tea ...
Back to the thread topic:
Just as MySQL starts to add Oracle type DB features (which Postgre has had for years) Oracle buys the MySQL "enterprise level" storage engine/table manager ... ouch.
What "secure transaction" alternatives does that leave MySQL?
MaxDB I guess ...
However it is also "dual licenced" just like InnoDB ...
Oracle may just be as warm and fuzzy as their initial press releases but if I was MySQL I would not bet the business on it.
Just how "nicely" will that contract "extension" be priced?
Just how soon will a "budget" Mini-Oracle be offered?
MyOracleSQL?
I think SQL Server is Oracle's target with MySQL being a convenient passing possible future competition target.
*nobody* in the PostgreSQL community refers to it as Postgre. The name is PostgreSQL, plain and simple. People sometimes abbreviate it to Postgres, especially verbally, but the prefered name is PostgreSQL.
PostgreSQL was originally called Postgres, then Postgres95, and now PostgreSQL. I speak of the current software, without the 's'. The 's' has been deprecated along with waving my pinky when drinking tea ...
It's either post-gres-q-l, or postgres for short. None of the developers refer to it as postgre, but that is a common mistake (even among people familiar with the database) for obvious reasons.
so...... does anyone know the connection string for Postgre(s) for ASP? I'd like to give it a try on my dev server before committing to it.
Did you happen to see the reply earlier by "iamlost":
connect_string = "Driver={Postgres}; Server=[server name]; Port=[port number]; Database=[database name]; UID=[username]; PWD=[password]"
