User number

Doom87

Hello i'm not very familiar with my sql or php so i thought i'd ask you guys. I want to have a user number issued for each database entry.

for example: first registration would be 1, second registration would be 2 and so on and so forth

I'm not sure how to do this can anybody help me please?

TheDefender

Create a primary key field, call it whatever (I use "tablename_id") to associate it with the table to which it corresponds. Then set the attributes to the field so it is INT(11) and set it to auto_increment.

Doom87

ok well the only thing i know how to do is make the table 'tablename_id

here's what i have:

CREATE TABLE tablename_id (
number varchar(10));

i'm not sure how to do anything else you said.

sorry i'm not very good at this stuff.

Sxooter

A couple of points.

TheDefender: What is up with all these int(11) things people keep using for stuff like this. honestly, just format your ints in php, it's easier and less confusing. And no, int(11) does NOT mean an 11 place int. And they're not transportable so any other db you use will puke on them. So please just stop it.

Doom87: You need to use an int type, not a varchar. Just use an int and declare it with autoincrement (see the mysql manual or whatever db you're using...)

TheDefender

Sxooter wrote:
A couple of points.

TheDefender: What is up with all these int(11) things people keep using for stuff like this. honestly, just format your ints in php, it's easier and less confusing. And no, int(11) does NOT mean an 11 place int. And they're not transportable so any other db you use will puke on them. So please just stop it.

Doom87: You need to use an int type, not a varchar. Just use an int and declare it with autoincrement (see the mysql manual or whatever db you're using...)

A simple, "Here's why int(11) is a bad idea" would've sufficed sxooter... I'm not sure where this hostility is coming from toward me because I think this is the first time I've personally ever made that recommendation and I haven't seen people knock it before; so before you go throwing phrases like "please just stop it" out there, consider your wording so as to not make inferences like that.

Sxooter

TheDefender wrote:
A simple, "Here's why int(11) is a bad idea" would've sufficed sxooter... I'm not sure where this hostility is coming from toward me because I think this is the first time I've personally ever made that recommendation and I haven't seen people knock it before; so before you go throwing phrases like "please just stop it" out there, consider your wording so as to not make inferences like that.

No, wasn't meaning to come across as hostile to you. honest. I'm just frustrated explaining it over and over on this forum and yet it keeps popping up. honest. It wasn't meant just for you. It was meant in a best practices kind of way. Sorry for the confusion.

Sadly, lots of people start using things like int(11) and they think they've got an 11 place int, and then, their int gets past 2^31-1 and explodes, and they didn't see it coming. That's all. It's mysql's fault for including such a confusing declaration. Wasn't mad at you, didn't mean to come across as it either. sorry.