Re:What ORMs have taught me: just learn SQL (2014)
by scarface74 on Monday December 18, 2017 @05:56AM
(#15950797)
Why is it an either or? EF can do that but then you loose the benefits of a type safe language.
[ Parent
| on HN ]
Re:What ORMs have taught me: just learn SQL (2014)
by oceanswave on Monday December 18, 2017 @07:45AM
(#15951236)
If type safety is so great, why isn’t sql statically type checked
Re:What ORMs have taught me: just learn SQL (2014)
by majewsky on Monday December 18, 2017 @08:22AM
(#15951402)
SQL is statically type-checked, at least in Postgres.
postgres=# SELECT * FROM domains WHERE id = 'foo';
ERROR: invalid input syntax for integer: "foo"
LINE 1: SELECT * FROM domains WHERE id = 'foo';
^
Re:What ORMs have taught me: just learn SQL (2014)
by cpfohl on Monday December 18, 2017 @08:42AM
(#15951510)
Not just PostGres. That's standard SQL. Columns have data types. Tables have schemata. Schemata are very strongly typed. Can't insert a 'full_name' column into a table without such a column.
Re:What ORMs have taught me: just learn SQL (2014)
by da_chicken on Monday December 18, 2017 @09:02AM
(#15951616)
Unless you're talking about SQLite, SQL RDBMSs are both static and strongly typed. The systems typically do allow some implicit type conversions, but type is critical to how a table works.
Re:What ORMs have taught me: just learn SQL (2014)
by lmm on Monday December 18, 2017 @11:05AM
(#15952558)
Because SQL predates a lot of modern techniques. A ground-up replacement written today probably would be statically type checked.