• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Database choices
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Database choices


  • Subject: Re: Database choices
  • From: Shehryar Khan <email@hidden>
  • Date: Tue, 30 Oct 2007 13:02:44 -0700


If you're going to use MySQL with WebObjects in a production environment, make sure to do the following:


- create all your tables with InnoDB engine support - the default MyISAM support is non-transactional

- make sure to create all your tables with the right charset and collation (UTF-8 all the way). MySQL's internationalization support is excellent but ONLY if configured properly.

- make sure to add the correct voodoo to the JDBC connection string for your application so that it uses the right charset / collation over the JDBC connection.

While MySQL has worked out quite well for us when used with WebObjects (and PHP), the lack of sequences makes it a less viable choice for projects going forward.

These days we go out of our way to design schemas that are WebObjects, Ruby on Rails, Hibernate, and PHP friendly. The MySQL / EO_PK_TABLE paradigm just doesn't fit well in this methodology - PostgreSQL is a much better choice.

thanks!

-shehryar

On Oct 30, 2007, at 11:42 AM, John Huss wrote:

For example, the FrontBase mail list archive has this message:

Subject: [RESOLVED] Re: Optimization/Caching/Indexing how-to

The order of the columns in the composite index definition is very important for your case.

If you want the optimal performance, you need to put the timestamp column last in the index definition because it is used with a range. The server cannot use the column of an index after one with a range qualifier.

For example, in your case, if your composite index is define like these example with a = check on fkY and fkZ and a range on dateX:
- (dateX, fkY, fkZ), only the date columsn is used like an index (dateX)
- (fkY, dateX, fkZ), only the fkY and date columsn is used like an index (fkY, dateX)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40ubermind.com


This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >Re: Database choices (From: Ricardo Parada <email@hidden>)
 >Re: Database choices (From: Mike Schrag <email@hidden>)
 >Re: Database choices (From: "John Huss" <email@hidden>)
 >Re: Database choices (From: Chuck Hill <email@hidden>)
 >Re: Database choices (From: "John Huss" <email@hidden>)

  • Prev by Date: Re: AJRDatabase + MiscMerge ?= NeoEOGenerator
  • Next by Date: Regarding Final Note
  • Previous by thread: Re: Database choices
  • Next by thread: Re: Database choices
  • Index(es):
    • Date
    • Thread