Do you develop on GitHub? You can keep using GitHub but automatically sync your GitHub releases to SourceForge quickly and easily with this tool so your projects have a backup location, and get your project in front of SourceForge's nearly 20 million monthly users. It takes less than a minute. Get new users downloading your project releases today!
I hate it when people develop God complexes. Just because you write books about something doesn't mean you invented it and are the Sole Speaker of the Truth®. And table primary key names. What an issue to be worked up over. At least the other guys (and yourself) are discussing things with relative calm. I'm afraid I'm unrefined enough that I always just use 'id' as an auto_increment int(11) and never look back. But then again I just make games and nonsense sites, not Important Software.
At least the other guys (and yourself) are discussing things with relative calm
Yeah.
Serge knows his stuff, and is generally likeable. His communication style could probably use some help though. But i don't mind.
The other guy has a point, though i believe him to be incorrect. Who knows, maybe i'll even learn something?:)
I do believe, however, in a SQL Server newsgroup i'd be laughed out for caring, and in an Oracle group i'd be praised for defending the "Truth", here though, in an IBM group, which stands o
I do believe, however, in a SQL Server newsgroup i'd be laughed out for caring, and in an Oracle group i'd be praised for defending the "Truth", here though, in an IBM group, which stands on both sides, it's a fight.
Well, we here at IBM like to support all sides. Part of our mandatory Diversity Training [slashdot.org], you know.
That's usually a good idea. Except, i like a TRIGGER intead of autoincrement which is just plain wrong, and int should be better than int(11).
Well, we here at IBM like to support all sides. Part of our mandatory Diversity Training, you know.
Heh.:)
But i think it hurts int he DB itself. With no clear path, people do as they wish, which then needs to be supported more, and the DB is optimized for nothing.
I find DB2 to be quite tedious to use effectively.
The day I build something that requires an id larger than int(11) is the day... I don't know. It won't be that day, though. And when I select int on my silly host's interface it defaults to int(11)
Scientists will study your brain to learn more about your distant cousin, Man.
IDs and ID10T's. (Score:2)
Re:IDs and ID10T's. (Score:2)
Yeah.
Serge knows his stuff, and is generally likeable. His communication style could probably use some help though. But i don't mind.
The other guy has a point, though i believe him to be incorrect. Who knows, maybe i'll even learn something?
I do believe, however, in a SQL Server newsgroup i'd be laughed out for caring, and in an Oracle group i'd be praised for defending the "Truth", here though, in an IBM group, which stands o
Re:IDs and ID10T's. (Score:2)
Well, we here at IBM like to support all sides. Part of our mandatory Diversity Training [slashdot.org], you know.
That's usually a good idea. Except, i like a TRIGGER intead of autoincrement which is just plain wrong, and int should be better than int(11).
The day I build something that requires an id
Re:IDs and ID10T's. (Score:2)
Heh.
But i think it hurts int he DB itself. With no clear path, people do as they wish, which then needs to be supported more, and the DB is optimized for nothing.
I find DB2 to be quite tedious to use effectively.
The day I build something that requires an id larger than int(11) is the day