Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: Using NULLS FIRST/LAST on sort orderings

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Using NULLS FIRST/LAST on sort orderings

Subject: Re: Using NULLS FIRST/LAST on sort orderings
From: Lachlan Deck <email@hidden>
Date: Wed, 7 Jan 2009 10:56:31 +1100

On 07/01/2009, at 4:29 AM, Miguel Arroz wrote:

Nop. Must be in the DB, it's too many data to handle in memory (the table that shows it is paged).

This is not achievable apart from in-memory. SQL does not allow for this. Period.

Your only choice is to not use NULL if you want to do this via the DB. NULLs are a special beast in DB land... good luck!

with regards,
--

Lachlan Deck

_______________________________________________
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


Follow-Ups:

Re: Using NULLS FIRST/LAST on sort orderings
From: Guido Neitzer <email@hidden>
Re: Using NULLS FIRST/LAST on sort orderings
From: Miguel Arroz <email@hidden>


References:  
  >Re: Using NULLS FIRST/LAST on sort orderings (From: James Cicenia <email@hidden>)
  >Re: Using NULLS FIRST/LAST on sort orderings (From: Miguel Arroz <email@hidden>)
  >Re: Using NULLS FIRST/LAST on sort orderings (From: James Cicenia <email@hidden>)
  >Re: Using NULLS FIRST/LAST on sort orderings (From: Miguel Arroz <email@hidden>)




Prev by Date:
Re: Not finding binding with "$^" notation

Next by Date:
Re: A relationship in a converted model now throws an exception on	save

Previous by thread:
Re: Using NULLS FIRST/LAST on sort orderings

Next by thread:
Re: Using NULLS FIRST/LAST on sort orderings

Index(es):

Date
Thread