Add Code of Conduct and CSVQ support with documentation updates.

.github/workflows/scorecard.yml

@@ -10,7 +10,8 @@ on:
     # For Branch-Protection check. Only the default branch is supported. See
     # https://github.com/ossf/scorecard/blob/main/docs/checks.md#branch-protection
     branch_protection_rule:
-    # To guarantee Maintained check is occasionally updated. See
+
+    # To guarantee, Maintained check is occasionally updated. See
     # https://github.com/ossf/scorecard/blob/main/docs/checks.md#maintained
     schedule:
       - cron: '36 3 * * 2'

CODE_OF_CONDUCT.md

@@ -0,0 +1,56 @@
+dmorph Community Code of Conduct
+=================================
+
+Like the technical community as a whole, the *dmorph* team and community is
+made up of a mixture of professionals and volunteers from all over the world,
+working on every aspect of the mission—including mentorship, teaching and
+connecting people.
+
+Diversity is one of our huge strengths, but it can also lead to communication
+issues and unhappiness. To that end, we have a few ground rules that we ask
+people to adhere to when they're participating within this community and
+project. These rules apply equally to founders, mentors, and those seeking help
+and guidance.
+
+This isn't an exhaustive list of things that you can't do. Rather, take it in
+the spirit in which it's intended—a guide to make it easier to enrich all of
+us, the technical community and the conferences and user groups we hope to guide
+new speakers to.
+
+This code of conduct applies to all communication: this includes IRC, the
+mailing list, and other forums such as Skype, Google+ Hangouts, etc.
+
+* __Be welcoming, friendly, and patient.__
+
+* __Be considerate.__ Your work will be used by other people, and you in turn
+  will depend on the work of others. Any decision you make will affect users and
+  colleagues, and you should take into account those consequences when making
+  decisions.
+
+* __Be respectful.__ Not all of us will agree all the time, but disagreement is
+  no excuse for poor behavior and poor manners. We might all experience some
+  frustration now and then, but we cannot allow that frustration to turn into a
+  personal attack. It's important to remember that a community where people feel
+  uncomfortable or threatened is not productive. Members of the *dmorph*
+  community should be respectful when dealing with other members as well as with
+  people outside the *dmorph* community and with user groups/conferences,
+  user group/conference organizers.
+
+* __Be careful in the words that you choose.__ Remember that sexist, racist, and
+  other exclusionary jokes can be offensive to those around you. Be kind to
+  others. Do not insult or put down other participants. Behave professionally.
+  Remember that harassment and sexist, racist, or exclusionary jokes are not
+  appropriate for the community.
+
+__When we disagree, we try to understand why.__ Disagreements, both social and
+technical, happen all the time and *dmorph* is no exception. It is important
+that we resolve disagreements and differing views constructively. Remember that
+we're different. The strength of *dmorph* comes from its varied community,
+people from a wide range of backgrounds. Different people have different
+perspectives on issues. Being unable to understand why someone holds a viewpoint
+doesn't mean that they're wrong. Don't forget that it is human to err and
+blaming each other doesn't get us anywhere, rather offer to help resolving
+issues and to help learn from mistakes.
+
+*Original text courtesy of the
+[Speak Up! project](http://web.archive.org/web/20141109123859/http://speakup.io/coc.html).*

README.md

@@ -72,6 +72,7 @@ necessary.
 
 Includes direct support for the following relational database management systems:
 
+* [CSVQ](https://mithrandie.github.io/csvq/)
 * [IBM Db2](https://www.ibm.com/db2/)
 * [Microsoft SQL Server](https://www.microsoft.com/sql-server)
 * [MySQL](https://www.mysql.com/) & [MariaDB](https://mariadb.org/)
@@ -107,7 +108,7 @@ A migration is a series of steps, defined either in an SQL file or programmatica
 A typical migration file consists of a sequence of SQL statements. Each statement needs to be
 finalized with a semicolon `;`. If a semicolon is found alone at the beginning of a line, all
 previous statements, that were not yet executed, are executed in one call to Exec in a
-transaction. A migration is executed completely inside of a transaction. If any of the steps of
+transaction. A migration is executed completely inside a transaction. If any of the steps of
 a migration fails, a rollback is issued and the process stops. Take care, that not all database
 management systems offer a rollback of DDL (CREATE, DROP, ...) statements.
 
@@ -216,7 +217,7 @@ func (m CustomMigration) Migrate(tx *sql.Tx) error {
 }
 ```
 
-Inside of the `Migrate` function the transaction state should not be modified.
+Inside the `Migrate` function the transaction state should not be modified.
 `Commit` and `Rollback` are handled by *DMorph* as needed. As seen in the example, a potentiel error
 is returned plain to the caller.
 

dialects_test.go

@@ -21,6 +21,7 @@ func TestDialectStatements(t *testing.T) {
 		name   string
 		caller func() BaseDialect
 	}{
+		{name: "CSVQ", caller: DialectCSVQ},
 		{name: "DB2", caller: DialectDB2},
 		{name: "MSSQL", caller: DialectMSSQL},
 		{name: "MySQL", caller: DialectMySQL},