Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

And then I ask, hey, where's my BOOLEAN? And then I drink.


Oh god.

And the lack of a serial/autoincrement/identity type.

So. Many. Effing. Triggers.

And 32-character identifiers.

sigh


It's so much better to use a database that only allows one autoincrementing value per record, or one TIMESTAMP and then only allows you to have either a create timestamp or an update timestamp without writing a trigger.

I prefer the way Oracle does it, you may have to do more work but it's more explicit and flexible that way.


I don't. I prefer for the common case to be correctly and automatically handled for me.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: