Opinions wanted: MySQL and Oracle Decision
- From: Libertarian <googer@xxxxxxxxxx>
- Date: Sat, 21 Jan 2006 14:34:16 -0500
About to embark on a new project... no customer at this time.
I've narrowed the backend choices down to MySQL and Oracle (partly a tech decision, partly a market reality decision). In a world without constraints, I'd choose Oracle since I have used it since version 7 and I can really leverage the proprietary bits if allowed to.
MySQL 5.0 on the other hand is a close contender. It's not quite Oracle, but you can see it from there.
The driving factor in my decision is what will my "potential" customers like: MySQL or Oracle. Many potential customers have flexible site licenses and existing ties to Oracle... my app would be a negigible $ addtion. However, many smaller customers can only afford MySQL. So who to target...?
It will be about 2 years before I know who will like my product... Oracle Shops or Shoe-string Shops. So I'll start development using generic ANSI SQL to the max extent possible. I think, but am unsure, I can proceed with development friendly to both.
Some Q's:
1. Are the trigger/package capabilities in MySQL are similiar to Oracle?
2. How far can one go down the develop road before they are married to a backend? (there's high bad joke potential for that stmt)
3. Cognizant of the potential need to change backend db's in the future, which would you start development with today: MySQL, Oracle, other?
Other thougts... .
- Follow-Ups:
- Re: Opinions wanted: MySQL and Oracle Decision
- From: Richard Wheeldon
- Re: Opinions wanted: MySQL and Oracle Decision
- From: HansF
- Re: Opinions wanted: MySQL and Oracle Decision
- From: Roedy Green
- Re: Opinions wanted: MySQL and Oracle Decision
- Prev by Date: Re: mysql-connector-java-3.1.7-bin.jar
- Next by Date: Re: safety of where =
- Previous by thread: mysql-connector-java-3.1.7-bin.jar
- Next by thread: Re: Opinions wanted: MySQL and Oracle Decision
- Index(es):
Relevant Pages
|
|
