ORMs are something that seem cool until you have to do anything with them, and then they just get in the way. Their promises (backend-agnostic, write type-safe native code, less boilerplate) sometimes have a catch and sometimes are just false.
The reason for this is that ORMs are backwards: they force you to design schemas in your implementation language (python, javascript, java) and then export them to #sql ‘somehow’. (The ‘somehow’ is usually a half-baked migration tool). This is bad for a lot of reasons and horrible if you want to access your data from another language.
The reason for this is that ORMs are backwards: they force you to design schemas in your implementation language (python, javascript, java) and then export them to #sql ‘somehow’. (The ‘somehow’ is usually a half-baked migration tool). This is bad for a lot of reasons and horrible if you want to access your data from another language.
3rd October 2019: PostgreSQL 12 Released! #sql
Changelog: https://www.postgresql.org/docs/12/release-12.html
Changelog: https://www.postgresql.org/docs/12/release-12.html
Open-sourcing Polynote: an IDE-inspired polyglot notebook:
> We are pleased to announce the open-source launch of Polynote: a new, polyglot notebook with first-class Scala support, Apache Spark integration, multi-language interoperability including #scala, #python, and #sql, as-you-type autocomplete, and more.
https://polynote.org/
> We are pleased to announce the open-source launch of Polynote: a new, polyglot notebook with first-class Scala support, Apache Spark integration, multi-language interoperability including #scala, #python, and #sql, as-you-type autocomplete, and more.
https://polynote.org/
sqlmap is an open source penetration testing tool that automates the process of detecting and exploiting #sql injection flaws and taking over of database servers. It comes with a powerful detection engine, many niche features for the ultimate penetration tester, and a broad range of switches including database fingerprinting, over data fetching from the database, accessing the underlying file system, and executing commands on the operating system via out-of-band connections.
https://github.com/sqlmapproject/sqlmap
#python
https://github.com/sqlmapproject/sqlmap
#python
sql-lint is a linter for SQL, it brings back any error from the supported servers as well as custom errors written for sql-lint.
sql-lint will show errors about the following things (and more)
- DELETE statements missing WHERE clauses
- DROP/TRUNCATE/ALTER/CREATE statements with invalid options specified
- Odd code points in queries
- Invalid arguments to the LIMIT clause
- Any SQL server errors
sql-lint brings back errors from the supported servers too. It will catch any error from the server. these include but are not limited to:
- Unknown columns on a table
- A non existent database
- A non existent table
- Syntax errors
https://github.com/joereynolds/sql-lint
#ts #sql
sql-lint will show errors about the following things (and more)
- DELETE statements missing WHERE clauses
- DROP/TRUNCATE/ALTER/CREATE statements with invalid options specified
- Odd code points in queries
- Invalid arguments to the LIMIT clause
- Any SQL server errors
sql-lint brings back errors from the supported servers too. It will catch any error from the server. these include but are not limited to:
- Unknown columns on a table
- A non existent database
- A non existent table
- Syntax errors
https://github.com/joereynolds/sql-lint
#ts #sql
#sql Style Guide
You can use this set of guidelines, fork them or make your own - the key here is that you pick a style and stick to it. To suggest changes or fix bugs please open an issue or pull request on GitHub.
These guidelines are designed to be compatible with Joe Celko's SQL Programming Style book to make adoption for teams who have already read that book easier. This guide is a little more opinionated in some areas and in others a little more relaxed. It is certainly more succinct where Celko's book contains anecdotes and reasoning behind each rule as thoughtful prose.
https://www.sqlstyle.guide/
You can use this set of guidelines, fork them or make your own - the key here is that you pick a style and stick to it. To suggest changes or fix bugs please open an issue or pull request on GitHub.
These guidelines are designed to be compatible with Joe Celko's SQL Programming Style book to make adoption for teams who have already read that book easier. This guide is a little more opinionated in some areas and in others a little more relaxed. It is certainly more succinct where Celko's book contains anecdotes and reasoning behind each rule as thoughtful prose.
https://www.sqlstyle.guide/
www.sqlstyle.guide
SQL style guide by Simon Holywell
A consistent code style guide for SQL to ensure legible and maintainable projects
A SQL database implemented purely in TypeScript type annotations.
This means that it operates solely on #ts types - you define a "database" (just a type annotation) and then query it using some more type annotations.
It supports a subset of #sql, including SELECT (with conditions and joins), INSERT, UPDATE and DELETE statements.
Personal opinion: crazy and super cool!
https://github.com/codemix/ts-sql
This means that it operates solely on #ts types - you define a "database" (just a type annotation) and then query it using some more type annotations.
It supports a subset of #sql, including SELECT (with conditions and joins), INSERT, UPDATE and DELETE statements.
Personal opinion: crazy and super cool!
https://github.com/codemix/ts-sql