here's an idea:
if you would have all emails stored in the reverse order:
moc.niamod@resu
then all you would need is simple 'ORDER BY email'.
Also, in this way, emails like [EMAIL PROTECTED] would be perfectly
ordered.
Is that a crazy thought?
If not yet then: why not to add an addit
Why is everyone else suggesting new functions? This works (in 6.5.3):
ORDER BY lower(substring(email from position('@' in email)+1 )),
lower(email)
remove the lower() functions if you don't need them (I had mixed case
addresses).
I am guessing/assuming that it's cheaper to just use entire e
Herve, Etc.
Ooops! A couple of misteaks in that last post:
> > [EMAIL PROTECTED]
> > [EMAIL PROTECTED]
> > [EMAIL PROTECTED]
> > [EMAIL PROTECTED]
> > [EMAIL PROTECTED]
> >
> > Is it possible and how ?
>
> Given the relational rule of Atomicity (each discrete piece of
> information shall have
Herve,
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
>
> Is it possible and how ?
Given the relational rule of Atomicity (each discrete piece of
information shall have its own column or row), the solution is for you
to make "e-mail id" and "
