7 ms·

"Don't use CURRENT_TIME. Never" Honest question. If we should never use it, why have it in the first place as an option ? Is it some type of backward compatibi

"Don't use CURRENT_TIME. Never" Honest question. If we should never use it, why have it in the first place as an option ? Is it some type of backward compatibility issue ? This list is great btw. Why we shouldn't do something is a great way to learn stuff.

monsieurbanana 7y ago
They give the reason on the previous entry (about timetz): > Why not? > Even the manual tells you it's only implemented for SQL compliance.
- k__ 7y ago
  lol, can't they implement a strict mode?
  - snazz 7y ago
    Do they? This doesn’t sound like a bad idea. Strict mode disabled = compatibility features on; strict mode enabled = only ‘safe’ options enabled.
    - k__ 7y ago
      I don't know, but somehow HN hates this idea?!
      - otterley 7y ago
        I suspect you're being downvoted not because of your idea, but because of how you're presenting it. Comments that contain "lol" and a sarcastic remark or rhetorical question are considered immature and aren't well accepted here.
deleted 7y ago
[deleted]
ape4 7y ago
Postgres could give a warning message for this (and other no-no's)
dgellow 7y ago
I have the same question for things such as > Don't use psql -W or psql --password If I do a psql --help I see Connection options: -W, --password force password prompt (should happen automatically) Nothing tells me I shouldn’t use it.
- LeonM 7y ago
  The documentation even states: > This option is never essential, since psql will automatically prompt for a password if the server demands password authentication. However, psql will waste a connection attempt finding out that the server wants a password. In some cases it is worth typing -W to avoid the extra connection attempt. So this is definitely confusing. What they probably mean is that you shouldn't do something like --password=mypassword, which will work but is obviously dangerous to do.
  - ambentzen 7y ago
    Don't do that either, but -W will always ask for a password even when one is not required. Got a keylogger or someone watching over your shoulder, and they now have your password even if the server is not actually asking for it. All that insecurity just to, potentially, save a roundtrip to the server.
    - eitland 7y ago
      > Got a keylogger or someone watching over your shoulder, and they now have your password even if the server is not actually asking for it. If this happens you've lost already, -W or not.
    - yellowapple 7y ago
      Why would I ever not want the server to require a password, though? Like, if your server ain't asking for a password at all, then why even bother with the keylogger?
      - samus 7y ago
Sahhaese 7y ago
It explains why, because it returns timetz which is only kept for compatibility with the SQL specification but is a bad way to store time.

monsieurbanana 7y ago

They give the reason on the previous entry (about timetz): > Why not? > Even the manual tells you it's only implemented for SQL compliance.

k__ 7y ago
lol, can't they implement a strict mode?
- snazz 7y ago
  Do they? This doesn’t sound like a bad idea. Strict mode disabled = compatibility features on; strict mode enabled = only ‘safe’ options enabled.
  - k__ 7y ago
    I don't know, but somehow HN hates this idea?!
    - otterley 7y ago
      I suspect you're being downvoted not because of your idea, but because of how you're presenting it. Comments that contain "lol" and a sarcastic remark or rhetorical question are considered immature and aren't well accepted here.

deleted 7y ago

[deleted]

ape4 7y ago

Postgres could give a warning message for this (and other no-no's)

dgellow 7y ago

I have the same question for things such as > Don't use psql -W or psql --password If I do a psql --help I see Connection options: -W, --password force password prompt (should happen automatically) Nothing tells me I shouldn’t use it.

LeonM 7y ago
The documentation even states: > This option is never essential, since psql will automatically prompt for a password if the server demands password authentication. However, psql will waste a connection attempt finding out that the server wants a password. In some cases it is worth typing -W to avoid the extra connection attempt. So this is definitely confusing. What they probably mean is that you shouldn't do something like --password=mypassword, which will work but is obviously dangerous to do.
- ambentzen 7y ago
  Don't do that either, but -W will always ask for a password even when one is not required. Got a keylogger or someone watching over your shoulder, and they now have your password even if the server is not actually asking for it. All that insecurity just to, potentially, save a roundtrip to the server.
  - eitland 7y ago
    > Got a keylogger or someone watching over your shoulder, and they now have your password even if the server is not actually asking for it. If this happens you've lost already, -W or not.
  - yellowapple 7y ago
    Why would I ever not want the server to require a password, though? Like, if your server ain't asking for a password at all, then why even bother with the keylogger?
    - samus 7y ago

Sahhaese 7y ago

It explains why, because it returns timetz which is only kept for compatibility with the SQL specification but is a bad way to store time.