Gaetano Mendola [EMAIL PROTECTED] writes:
Comments are welcomed.
Well as long as you're asking...
Email domains are case insensitive, but the left hand side is case sensitive.
That's the only part that's hard to handle using a text data type, it would be
kind of neat if the email operators
...
Another thing is that it might make more sense to sort email addresses by
domain first (case insensitively of course), then by left hand side (case
sensitively). Since the domain is really the most significant bit. This
is also convenient for many systems like email since they perform
Greg Stark wrote:
Gaetano Mendola [EMAIL PROTECTED] writes:
Comments are welcomed.
Well as long as you're asking...
Email domains are case insensitive, but the left hand side is case sensitive.
That's the only part that's hard to handle using a text data type, it would be
kind of neat if the
On Mon, May 17, 2004 at 17:11:42 +0200,
Gaetano Mendola [EMAIL PROTECTED] wrote:
That's true, I will order as Tommi Maekitalo suggest.
And how do domain literals fit into this?
[EMAIL PROTECTED] is a valid email address for me. (At least as
long as my server is at that IP address.)
Tommi Maekitalo [EMAIL PROTECTED] writes:
Sorting should then be done by top-level-domain first. Then 2nd, 3rd... and
last by user.
I thought of that but decided not to suggest it:
a) as far as email goes there's no relationship between [EMAIL PROTECTED] and
[EMAIL PROTECTED] The .com
I already post this message using [EMAIL PROTECTED]
with attached a binary file but I guess the newsgroup not
accept binary file.
The following was almost the message, now the file is on pg_foundry (
now it's working ).
=
Hi all,
