Skip to content
Permalink
Browse files

Get markdown-clj table parsing working

  • Loading branch information...
swlkr committed Mar 17, 2019
1 parent 739b1b9 commit ac13ba5dc4c57bc05d0c8c370dfedadf1857b8ef
Showing with 9 additions and 9 deletions.
  1. +1 −1 docs/database-getting-started.md
  2. +3 −3 docs/migrations.md
  3. +3 −3 docs/pull.md
  4. +1 −1 docs/queries.md
  5. +1 −1 docs/sessions.md
@@ -18,7 +18,7 @@ NOTE: Coast uses the [java.jdbc](https://github.com/clojure/java.jdbc) and hikar
The list of supported databases and their drivers:

| database | driver |
|:------------|:------------------------------------------------------|
| :------------ | :------------------------------------------------------ |
| postgresql | [pgjdbc](https://github.com/pgjdbc/pgjdbc) |
| sqlite3 | [sqlite-jdbc](https://github.com/xerial/sqlite-jdbc) |

@@ -82,7 +82,7 @@ This is the full list of column types supported by Coast migrations:
### Column Types
| function | description |
|:-------------|:-------------|
| :------------- | :------------- |
| text | adds a text column |
| timestamp | adds a timestamp column |
| datetime | adds a datetime column |
@@ -98,7 +98,7 @@ This is the full list of column types supported by Coast migrations:
This is the full list of column attributes you can pass into each column function
| key | value | description |
|:-------------|:------------|:-------------|
| :------------- | :------------ | :------------- |
| :collate | string | sets the column collation (e.g. `utf8_unicode`) |
| :null | true/false | adds "not null" if null is set to false |
| :unique | true/false | creates a unique constraint for this column |
@@ -115,7 +115,7 @@ Below is the list of available migration commands.
### Command List
| command | description |
|:---------|:-------------|
| :--------- | :------------- |
| `coast gen migration ` | creates a new migration file in `db/migrations` |
| `make db/migrate` | runs all pending migration files |
| `make db/rollback` | rolls back the most recent migration file |
@@ -84,8 +84,8 @@ Here's a quick walk through of defining a database migration with two tables and
This first migration defines an `author` table that looks like this:
| column | type |
|:--------|:------|
| column | type |
| :-------- | :------ |
| id | integer primary key |
| screen_name | text |
| email | text |
@@ -106,7 +106,7 @@ The second migration defines a `post` table:
```
| column | type |
|:--------|:------|
| :-------- | :------ |
| id | integer primary key |
| author | integer references author(id) |
| title | text |
@@ -60,7 +60,7 @@ The first thing you'll notice is that every response back from the database uses
Given this table named `person`
| column | type |
|:-------------|:-----------|
| :------------- | :----------- |
| id | integer |
| screen_name | text |
| email | text |
@@ -20,7 +20,7 @@ You can change the current store by adding one to your `deps.edn` file and speci
Note: The [redis](https://github.com/paraseba/rrss) and [jdbc](https://github.com/luminus-framework/jdbc-ring-session) stores are not included with coast by default.

| Name | Function | Description |
| ------------- |:--------------:| -------------------------------------------------------------------:|
| :------------ | :--------------: | :------------------------------------------------------------------: |
| Cookie | `cookie-store` | The default store used by coast, stores sessions in encrypted cookie|
| Memory | `memory-store` | In-memory store, all sessions will be reset on server restart |
| JDBC | `jdbc-store` | Stores the sessions in a database table |

0 comments on commit ac13ba5

Please sign in to comment.
You can’t perform that action at this time.