Posted by Dimitri Marshall on 07/29/06 14:53

Hey Guys,

Ya in my userAccounts table I use the e-mail address and username, although
in this case I did need a number of some sort. I did figure out
auto_increment and obviously it wasn't as hard as I was letting on. Anyway,
it was fun trying to make my own!

Thanks,

--
Dimitri Marshall

"David" <dgold1958@yahoo.de> wrote in message
news:20kjc2hf2qql9oa4h9q63bpjl90njsojut@4ax.com...
> On Thu, 27 Jul 2006 17:21:57 +0200, Cujo <fra@despammed.com> wrote:
>
>>Dimitri Marshall wrote:
>>
>>> Now, the reason I'm doing this is so I can create unique IDs for the
>>> stuff
>>> in my database.
>>
>>How is ORDER BY going to help you create unique id's ?
>>
>>> I know there is probably another way to do this but I
>>> thought this was the easiest
>>
>>There is only ONE way. Autoincrement.
>
> This is absolutely NOT a requirement to create uniqe ID's. You can
> generate your own unique ID's by combining fields as primary keys, for
> example. An email address can be a very good unique ID, too.
>
>>> (I couldn't figure out the whole auto_increment
>>> thing.
>>
>>There is nothing to figure out, really, besides reading the docs.
>>What exactly is your problem with auto increment ? I believe
>>it's worth learning how to do things like this properly.
>
> Not sure why you believe that autoincrement is the proper method in
> this case!? You need to examine your data and base your decisions on
> that. If I have a membership table, for instance, the member ID code
> is the perfect unique ID. How I generate the member ID can be based
> on parsing different fields, for example. Hint: I am currently doing
> this in a project that I am working on.
>
>>If you are more precise on what you're having problems with,
>>i might be able to help ...
>
>>regards, f.
>
> David
>

[Back to original message]