3 ms·

I don’t discuss which DB to use. I straight away use SQL. That is a language though, not a DB.

by TekMol 8y ago

SmellyGeekBoy 8y ago
In the .NET / Microsoft world "SQL" has been synonymous with "Microsoft SQL Server" for years. GP could just be from that background.
- corobo 8y ago
  Yup and if he was using PHP it'd almost certainly be MySQL. Your grizzled old Perl types would probably go with postgreSQL as an easy assumption
jmartrican 8y ago
I assumed he meant MySQL, but now that you bring it up I wonder what other people thought he meant?
- beaconstudios 8y ago
  I read it as one of MySQL/MariaDB/PostgresQL/MSSQL. AFAIK they're the canonical implementations now. Sqlite is too but that's embedded, so it's targeting a different use case.
kiloreux 8y ago
Did you really have to be that guy ? What he meant basically is using a relational database. Please refer to the HN guidelines before commenting. It strongly encourages to have comments that add value to the discussion.
- jazoom 8y ago
  I agree with TekMol that it's an important point. Nowadays we have new types of SQL databases emerging. Some examples: TiDB (distributed) CockroachDB (distributed) Crate (uses SQL but isn't even relational) They all use SQL. Picking between these and more established SQL databases is worthy of discussion. Heck, based on what I see on Hacker News, picking between the established ones generates a lot of discussion, usually with people preferring Postgres over MySQL, etc. Then there's SQLite, which is completely different again. OP probably has a favourite database as a go-to regardless of the application, but for some projects SQLite might be a better fit than the others, for example. That would warrant discussion. In conclusion, I believe you were too harsh to TekMol. Edit: Fix autocorrect fails and add clarity.
  - beaconstudios 8y ago
    one of the community practices here is that you should take the most charitable interpretation of what is written. This precludes nitpicking. It's clear that the OP was referring to "I just use SQL" in terms of picking the most mature/standard database approach (relational databases) instead of getting caught up in the quagmire of niche and specialist database schemas.
    - jazoom 8y ago
      That might not be so obvious to someone who isn't familiar with SQL databases. To those people, the "nitpick" added clarity.
  - deleted 8y ago
    [deleted]

I don’t discuss which DB to use. I straight away use SQL. That is a language though, not a DB.

by TekMol 8y ago

I don’t discuss which DB to use. I straight away use SQL. That is a language though, not a DB.

In the .NET / Microsoft world "SQL" has been synonymous with "Microsoft SQL Server" for years. GP could just be from that background.

corobo 8y ago
Yup and if he was using PHP it'd almost certainly be MySQL. Your grizzled old Perl types would probably go with postgreSQL as an easy assumption

jmartrican 8y ago

I assumed he meant MySQL, but now that you bring it up I wonder what other people thought he meant?

beaconstudios 8y ago
I read it as one of MySQL/MariaDB/PostgresQL/MSSQL. AFAIK they're the canonical implementations now. Sqlite is too but that's embedded, so it's targeting a different use case.

kiloreux 8y ago

Did you really have to be that guy ? What he meant basically is using a relational database. Please refer to the HN guidelines before commenting. It strongly encourages to have comments that add value to the discussion.

jazoom 8y ago
I agree with TekMol that it's an important point. Nowadays we have new types of SQL databases emerging. Some examples: TiDB (distributed) CockroachDB (distributed) Crate (uses SQL but isn't even relational) They all use SQL. Picking between these and more established SQL databases is worthy of discussion. Heck, based on what I see on Hacker News, picking between the established ones generates a lot of discussion, usually with people preferring Postgres over MySQL, etc. Then there's SQLite, which is completely different again. OP probably has a favourite database as a go-to regardless of the application, but for some projects SQLite might be a better fit than the others, for example. That would warrant discussion. In conclusion, I believe you were too harsh to TekMol. Edit: Fix autocorrect fails and add clarity.
- beaconstudios 8y ago
  one of the community practices here is that you should take the most charitable interpretation of what is written. This precludes nitpicking. It's clear that the OP was referring to "I just use SQL" in terms of picking the most mature/standard database approach (relational databases) instead of getting caught up in the quagmire of niche and specialist database schemas.
  - jazoom 8y ago
    That might not be so obvious to someone who isn't familiar with SQL databases. To those people, the "nitpick" added clarity.
- deleted 8y ago
  [deleted]