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 ".co
Bruno Wolff III wrote:
On Mon, May 17, 2004 at 18:01:43 +0200,
Gaetano Mendola <[EMAIL PROTECTED]> wrote:
Well I think that accept an email like:
[EMAIL PROTECTED]
Be careful about this. [EMAIL PROTECTED] is not the same as
[EMAIL PROTECTED]] .
Not wanting to r
On Mon, May 17, 2004 at 18:01:43 +0200,
Gaetano Mendola <[EMAIL PROTECTED]> wrote:
> Well I think that accept an email like:
>
> [EMAIL PROTECTED]
Be careful about this. [EMAIL PROTECTED] is not the same as
[EMAIL PROTECTED] .
---(end of broadcast)-
On Mon, May 17, 2004 at 17:01:36 +0200,
Gaetano Mendola <[EMAIL PROTECTED]> wrote:
>
> Also the validator will validate emails in this form, if you are thinking to
> validate emails as:
>
> "Gaetano M. Public"(junior)
That appears to be an rfc 2822 address. RFC 2821 addresses are more limited
It's rumoured that Steve Atkins once said:
> On Mon, May 17, 2004 at 05:01:05PM +0100, Dave Page wrote:
>
>> > [EMAIL PROTECTED] is syntactically valid. [EMAIL PROTECTED] is
>> > syntactically valid, but should be immediately rejected.
>>
>> I disagree - just because the database server cannot veri
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.)
On Monday 17 May 2004 8:45 am, Steve Atkins wrote:
> Also, [EMAIL PROTECTED] is a syntactically valid email address, in the
> .13 TLD. It does not deliver to 10.11.12.13, or anywhere else, as
> of today, unless the MTA or local recursive resolver is broken (a
> common case). [EMAIL PROTECTED] is a
On Mon, May 17, 2004 at 09:21:54AM -0700, Steve Crawford wrote:
> Along those lines [EMAIL PROTECTED] and [EMAIL PROTECTED] are valid but they
> don't necessarily refer to the same mailbox (depends on the mx for
> foo.bar.com).
I don't believe the latter is actually valid, as it has to be an
ad
> -Original Message-
> From: Gaetano Mendola [mailto:[EMAIL PROTECTED]
> Sent: 17 May 2004 17:02
> To: Dave Page
> Cc: Bruno Wolff III; [EMAIL PROTECTED]
> Subject: Re: [HACKERS] Email data type
>
>
> Well I think that accept an email like:
>
>
On Mon, May 17, 2004 at 05:01:05PM +0100, Dave Page wrote:
> > [EMAIL PROTECTED] is syntactically valid. [EMAIL PROTECTED] is
> > syntactically valid, but should be immediately rejected.
>
> I disagree - just because the database server cannot verify the the
> existence of a domain does not mea
> -Original Message-
> From: Steve Atkins [mailto:[EMAIL PROTECTED]
> Sent: 17 May 2004 16:46
> To: [EMAIL PROTECTED]
> Subject: Re: [HACKERS] Email data type
>
> [EMAIL PROTECTED] is syntactically valid. [EMAIL PROTECTED] is
> syntactically valid, but should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dave Page wrote:
|>-Original Message-
|>From: Gaetano Mendola [mailto:[EMAIL PROTECTED]
|>Sent: 17 May 2004 16:02
|>To: Bruno Wolff III
|>Cc: [EMAIL PROTECTED]
|>Subject: Re: [HACKERS] Email data type
|>
|>About the dom
> From: Gaetano Mendola [mailto:[EMAIL PROTECTED]
>
> I think I have to discard also the addresses with last octet
> equal to 256.
>
> Any comments ?
>
Any octet that contains a number less than 0 or greater than 255 should be
suspect.
Assuming you really meant 255:
It would be perfectly l
On Mon, May 17, 2004 at 05:01:36PM +0200, Gaetano Mendola wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Bruno Wolff III wrote:
>
> | On Sun, May 16, 2004 at 04:36:55 +0200,
> | Gaetano Mendola <[EMAIL PROTECTED]> wrote:
> |
> |>The type is indexable and provide also conversion me
> -Original Message-
> From: Gaetano Mendola [mailto:[EMAIL PROTECTED]
> Sent: 17 May 2004 16:02
> To: Bruno Wolff III
> Cc: [EMAIL PROTECTED]
> Subject: Re: [HACKERS] Email data type
>
> About the domain literals, I think to validate it in the near
> futur
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 em
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bruno Wolff III wrote:
| On Sun, May 16, 2004 at 04:36:55 +0200,
| Gaetano Mendola <[EMAIL PROTECTED]> wrote:
|
|>The type is indexable and provide also conversion methods:
|>
|>text <--> email
|>and the operator >>, is possible use it in select like:
...
>
> 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 perfo
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
On Sun, May 16, 2004 at 04:36:55 +0200,
Gaetano Mendola <[EMAIL PROTECTED]> wrote:
>
> The type is indexable and provide also conversion methods:
>
> text <--> email
> and the operator >>, is possible use it in select like:
When you are converting between text and email data, what format are t
Gaetano Mendola wrote:
Hi all, this is the alpha version for the new email data type,
is not written as built in type but as plug in, Tome Lane and others
drove me in this direction.
The type is indexable and provide also conversion methods:
text <--> email
and the operator >>, is possible use it i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all, this is the alpha version for the new email data type,
is not written as built in type but as plug in, Tome Lane and others
drove me in this direction.
The type is indexable and provide also conversion methods:
text <--> email
and the operator >
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, t
23 matches
Mail list logo
