> Oracle will sell it if they can convince the customer.
Any one who has had the pleasure of using Oracle Application Server
can attest to that.
--
- michael dykman
- mdyk...@gmail.com
May the Source be with you.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
database. I would also bet that 80% of the people who are actually
writing queries with that many joins don't have a solid grasp of the
fundamental principles of relational database design.
Why not? Normalizing gets you -more- tables, not less.
And normalizing is a goal in itself? I've seen
Martijn Tonies wrote:
Martijn Tonies wrote:
database. I would also bet that 80% of the people who are actually
writing queries with that many joins don't have a solid grasp of the
fundamental principles of relational database design.
Why not? Normalizing gets you -more- tables, not less.
A
Tom,
I noticed the article didn't say how much money you'll save by not paying
through the nose for Oracle per server licensing, the cost of upgrading
your hardware to get some speed out of Oracle, or the cost of having to
hire one or more Oracle administrators to manage and tweak the database.
Martijn Tonies wrote:
database. I would also bet that 80% of the people who are actually
writing queries with that many joins don't have a solid grasp of the
fundamental principles of relational database design.
Why not? Normalizing gets you -more- tables, not less.
And normalizing is a g
joins?
Oracle will sell it if they can convince the customer.
Just some thoughts.
- Original Message -
From: "Tom Worster"
To: "mos" ;
Sent: Sunday, January 31, 2010 7:39 PM
Subject: Re: 50 things to know before migrating from Oracle to MySQL
On 1/29/10 5:0
On 1/29/10 5:03 PM, "mos" wrote:
> I noticed the article didn't say how much money you'll save by not paying
> through the nose for Oracle per server licensing, the cost of upgrading
> your hardware to get some speed out of Oracle, or the cost of having to
> hire one or more Oracle administrators
On 01/29/2010 07:24 PM, Shawn Green wrote:
> Rudy Lippan wrote:
>> On 01/29/2010 02:57 PM, Chris W wrote:
>>
>>> Hardcore stupid if you ask me. I suppose it is "possible" to have a
>>> valid reason (can't imagine what it might be) for using more than 61
>>
>> How about complex data requirements?
Rudy Lippan wrote:
How about complex data requirements? Depending on the resolution of
your data set, I could see a "simple" person-type object that contained
name, address, SSN, mother, and birth_info starting to approach the limit.
Cities change, address changes, names change, and even mother
Martijn Tonies wrote:
database. I would also bet that 80% of the people who are actually
writing queries with that many joins don't have a solid grasp of the
fundamental principles of relational database design.
Why not? Normalizing gets you -more- tables, not less.
And normalizing is a goa
Rudy Lippan wrote:
On 01/29/2010 02:57 PM, Chris W wrote:
Hardcore stupid if you ask me. I suppose it is "possible" to have a
valid reason (can't imagine what it might be) for using more than 61
How about complex data requirements? Depending on the resolution of
your data set, I could see a
On 01/29/2010 02:57 PM, Chris W wrote:
> Hardcore stupid if you ask me. I suppose it is "possible" to have a
> valid reason (can't imagine what it might be) for using more than 61
How about complex data requirements? Depending on the resolution of
your data set, I could see a "simple" person-ty
... or 50 ways to leave your Oracle...
... or 50 ways to save your money...
Choose mysql! :)
--
Jørn Dahl-Stamnes
homepage: http://www.dahl-stamnes.net/dahls/
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arc
as a relatively unsophisticated dbms user (just dynamic web site back
end),
i thought it was very interesting to see the kinds of things oracle users
do
that i'd never have imagined.
more than 61 joins in a query?! man, those guys are hardcore.
Hardcore stupid if you ask me. I suppose it i
At 01:57 PM 1/29/2010, Chris W wrote:
fsb wrote:
as a relatively unsophisticated dbms user (just dynamic web site back end),
i thought it was very interesting to see the kinds of things oracle users do
that i'd never have imagined.
more than 61 joins in a query?! man, those guys are hardcore.
fsb wrote:
as a relatively unsophisticated dbms user (just dynamic web site back end),
i thought it was very interesting to see the kinds of things oracle users do
that i'd never have imagined.
more than 61 joins in a query?! man, those guys are hardcore.
Hardcore stupid if you ask me. I
25. Each table can have a different storage backend (”storage engine”).
Yes, we absolutely allow this.
Each engine brings a certain strength to the storage and retrieval
solutions you can create with MySQL. We explicitly recognize that there is
no "one size fits all" approach that meets the ne
51st
thing or if somebody emailed him one more thing.
- Original Message -
From: "Carl"
To:
Sent: Thursday, January 28, 2010 4:56 PM
Subject: Re: 50 things to know before migrating from Oracle to MySQL
A quick Google turned up
http://www.xaprb.com/blog/2009/03/13/50-thin
On 1/28/10 5:21 AM, "changuno" wrote:
> Hi folks,
>
> Read a blog which states 50 things to know before migrating from Oracle to
> MySQL. Any comments on this?
as a relatively unsophisticated dbms user (just dynamic web site back end),
i thought it was very interesti
- Original Message - From: "Daevid Vincent"
>
> To:
> Cc: "'changuno '"
> Sent: Thursday, January 28, 2010 5:49 PM
> Subject: RE: 50 things to know before migrating from Oracle to MySQL
>
>
> -Original Message-
>>> From:
9 PM
Subject: RE: 50 things to know before migrating from Oracle to MySQL
-Original Message-
From: John Meyer [mailto:johnme...@pueblocomputing.com]
Sent: Thursday, January 28, 2010 2:16 PM
To: mysql@lists.mysql.com
On 1/28/2010 3:21 AM, changuno wrote:
> Read a blog which states 5
> -Original Message-
> From: John Meyer [mailto:johnme...@pueblocomputing.com]
> Sent: Thursday, January 28, 2010 2:16 PM
> To: mysql@lists.mysql.com
>
> On 1/28/2010 3:21 AM, changuno wrote:
> > Read a blog which states 50 things to know before migrating
>
On 1/28/2010 3:21 AM, changuno wrote:
Hi folks,
Read a blog which states 50 things to know before migrating from Oracle to
MySQL. Any comments on this?
would it have been too much to just link to it?
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To
Shawn Green wrote:
> 23. There are fewer and less sophisticated tools for administration.
>
> MySQL doesn't need them. That alone should tell you something about
> our reliability.
>
This speaks to simplicity-- both in terms of easy to use and in terms of
more limited features. It says nothing
changuno wrote:
Hi folks,
Read a blog which states 50 things to know before migrating from Oracle to
MySQL. Any comments on this?
... list snipped ...
MySQL was never designed to be a clone of Oracle (the database). We
have distinct differences in design and implementation that make us a
anguno wrote:
> Hi folks,
>
> Read a blog which states 50 things to know before migrating from Oracle to
> MySQL. Any comments on this?
>
> 1. Subqueries are poorly optimized.
> 2. Complex queries are a weak point.
> 3. The query executioner (aka query optimize
Hi folks,
Read a blog which states 50 things to know before migrating from Oracle to
MySQL. Any comments on this?
1. Subqueries are poorly optimized.
2. Complex queries are a weak point.
3. The query executioner (aka query optimizer / planner) is less
sophisticated.
4. Performance
27 matches
Mail list logo
