• 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: Oracle and Sorting Null Values - everyone thinks different - everyone is correct
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Oracle and Sorting Null Values - everyone thinks different - everyone is correct


  • Subject: Re: Oracle and Sorting Null Values - everyone thinks different - everyone is correct
  • From: email@hidden
  • Date: Mon, 11 Jan 2010 15:15:17 -0500


Thanks Dave,

A property is cool so long as it has a default behavior that remains the status quo.

Still, this is a tough nut to crack in the general case with a simple flag because you have to account for both:

a) in-memory sorting - plus localization sorting issues

b) db sorting

I kind of think a wiki page is more practical.

This is just one of many cases where you have to realize the "objects" we deal with are later being stored / retrieved in a relational database. We think with objects but we don't have an object database. You realize this and say "that stinks" but you deal with it because the EOF illusion of being pure objects is pretty darn close.

Another option for you would probably be to adjust the NLS properties, or whatever they're called, in Oracle. Set the preference in Oracle to handle null sorting. No mucking with WO / EOF in this case.

Many ways to skin the cat.

Cheers,
-- Aaron


David Avendasora <email@hidden> wrote on 01/11/2010 12:23:28 PM:

> Hi Aaron!

>
> On Jan 11, 2010, at 10:29 AM, email@hidden wrote:

>
> In summary, it doesn't matter if you "fix" the DB or you fix the in-
> memory sorting as we have done. What matters is that you realize
> there can be differences and you have full control over how you want
> sorting to work no matter what DB you use.

>
> I agree completely. Sorting nulls isn't technically valid in the
> first place but in practical terms you need to do something with
> them. Since we have conflicting needs, I think we should come up
> with a property that will define how nulls are sorted so that both
> your solution and a DB-specific one (if available) are triggered
> based on the preference.

>
> something along the lines of: nullSortOrdering=first/last

>
> What do you think?

>
> Based on your email, I will update the Jira PATCH ticket I submitted
> to hold off on applying it so we can better address this.

>
> Dave
 _______________________________________________
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: Oracle and Sorting Null Values - everyone thinks different - everyone is correct (From: David Avendasora <email@hidden>)

  • Prev by Date: Re: WO 5.4.3 vs WO 5.3.3
  • Next by Date: Re: WO 5.4.3 vs WO 5.3.3
  • Previous by thread: Re: Oracle and Sorting Null Values - everyone thinks different - everyone is correct
  • Next by thread: WO 5.4.3 vs WO 5.3.3
  • Index(es):
    • Date
    • Thread