Hacker News new | ask | show | jobs
by ssijak 2944 days ago
That sounds dumb (if column type is called like that text in the quotes)
4 comments
fphilipe 2943 days ago
Might sound "dumb" or confusing (which it is), but makes a lot of sense. I've written a post explaining the difference between "timestamp with/without time zone": http://phili.pe/posts/timestamps-and-time-zones-in-postgresq...
link
da_chicken 2944 days ago
Why? If you're doing things correctly, you don't need to specify data types particularly often in SQL. You specify it once when the table is created and that's it. All you care about on the programming interface is that your application knows what data type of your language to use with each data column. What's wrong with a verbose and descriptive name for a data type?
link
kbrackbill 2944 days ago
I don't think they're saying that having verbose name is dumb, I think it's that a type called "timestamp with time zone" doesn't actually store a time zone.
link
da_chicken 2944 days ago
Yeah, that's what I initially thought, too, but some of the other responses have made me question that.
link
Erwin 2944 days ago
SQL data types have some verbose names, like "NATIONAL CHARACTER VARYING (20)". PG adds a "TIMESTAMPTZ" as alias for "TIMESTAMP WITH TIME ZONE" (which I'm not sure whether is a sql ansi standard type or just convention).
link
rspeele 2944 days ago
It is, and it is.
link