No post body was provided.
Ask HN: Db column naming: snake_case vs. CamelCase, what's the best convention?
1–6 of 6 posts
Re: Ask HN: Db column naming: snake_case vs. CamelCase, what's the best convention?
#2snake_case because if your column ends up in a Postgres/MySQL environment your CamelCase will be become camelcase
And reading those becomes nightmares
If you are just working in Javascript/Node.js, CamelCase is the preferred option.
Re: Ask HN: Db column naming: snake_case vs. CamelCase, what's the best convention?
#3It's camelCase, not CamelCase
I believe this is PascalCase
Re: Ask HN: Db column naming: snake_case vs. CamelCase, what's the best convention?
#4SHOUTY_CASE
Re: Ask HN: Db column naming: snake_case vs. CamelCase, what's the best convention?
#5Depending upon how you organize the words within them (*_id, *_name, *_percent), snake case allows you to parse the column names dynamically for things like santization and formatting.
Re: Ask HN: Db column naming: snake_case vs. CamelCase, what's the best convention?
#6SHOUTY_CASE
Snowflake forces this, so you would also never get CamelCase w/o always quoting the column name in your queries.