knexed
Adds some neatness to Knex library. Utilities for tables, joins, transactions and other.
why?
There're three ways to work with relational DB on an application side: raw SQL, query builders, ORMs.
I prefer query builders over other two and find it a perfect balance.
- why not raw SQL: I love SQL and plain queries, but it lacks two main features from application's view: composability and type control. By composability I mean that I can create query with multiple variative clauses and not bother with string glueing, putting spaces and commas here and there. By type control I mean bi-directional type conversions and data escaping. Both theese issues are perfectly solved by query builders.
- why not ORM: I dislike ORMs because they compel me for specific application structure, to use special type-wrappers and stateful data workflow. They often have ugly verbose API, poor performance, crazy output queries and bring no benefits comparing to query builders. On the other hand query builders work with native language types and encourage functional data-flow instead of «statefulness».
The lead query builder in JS ecosystem is Knex. I don't like it much for poor code style & architecture, not so good API. Yes, Knex is not perfect, however this is the leading project in this area and it tends to stay so. It working, it will receive updates, fixes and improves. I decided to build a better abstractions over it with composability and much more JS/Lispy-crazy-science-style in mind. The only restriction is not to fall into ORM-ish style. So this library contains only simple helpers and composable abstractions. Feel free to use another good solutions (like Bluebird's Promise extensions which is built-in for Knex, Lodash/fp, Ramda & lenses etc) along the way.
API
Import / require modules you need explicitly. Most of functionality is accessible from the root of the package, like require('knexed/one')
, require('knexed/exists')
. Some utilities are bundled into groups by usage, like require('knexed/table/table')
, require('knexed/table/join')
. The group of utility is mentioned in the braces below.
dataset helpers (./
)
knex('table').select()
.then(one)
.then(one.maybe)
.then(exists)
.then(exists.not)
.then(count)
.then(project('id'))
table helpers (table/table
)
var accounts = table(knex, 'accounts')
accounts().select()
accounts(trx).select()
accounts.as('alias').select()
accounts.as('alias', trx).select()
transaction helpers (tx/method
)
method
helper allows function to both be initial point in transaction, or consecutive.
If no transaction is passed as first argument, transaction well be initialized automatically.
If transaction is passed, method will accept it.
var create = method(knex, (trx, name) =>
{
return accounts(trx).insert({ name })
})
create(trx, 'Name')
create('Name')
create(method.NOTX, 'Name')
var m = method(knex)
var create = m((trx, name) => { … })
join helpers (table/join
)
Use join
helper for symmetric-looking joins. table
is used as basis.
var accounts = table(knex, 'accounts')
var messages = table(knex, 'messages')
var accounts$messages = join(accounts, messages, [ 'id', 'user_id' ])
accounts$messages()
.select('user_id', 'text')
.where('user_id', user_id)
accounts$messages(trx).select()
join.left(accounts, messages, [ 'id', 'user_id' ])
join.right(messages, accounts, [ 'id', 'user_id' ])
join.full(table_a, table_b, [ 'id', 'user_id' ])
join.cross(table_a, table_b)
join(accounts, messages, [ 'id', '=', 'user_id' ])
join.left(accounts, messages, [ 'id', '<>', 'user_id' ])
join(accounts, messages, 'id')
join([ accounts, 'A' ], [ messages, 'M' ], [ 'id', 'user_id' ])
query helpers (query
)
This helpers transform generated query.
var accounts = table(knex, 'accounts')
var q = accounts().where('id', '>', 1000)
var qc = count(q)
var qe = exists(q)
Note that count
& exists
from dataset helpers works on returning
dataset, which means streaming potentially large amount of redundant data from
database driver to client. In contrast query/count
& query/exists
works on driver's side, sending to client only simple scalars.
catch constraints (catch/constraint
)
Catch constraints and rethrow them as your model-specific constraint errors.
var accounts = table(knex, 'accounts')
function AlreadyExists ()
{
return new TypeError('account_already_exists')
}
accounts()
.insert({ id: 1, name: 'account' })
.catch(...catch_constraint('accounts_pkey', AlreadyExists))
var accounts = table(knex, 'accounts')
function AlreadyExists (data)
{
return { error: 'account_already_exists', conflict: data }
}
var id = 1
accounts()
.insert({ id, name: 'account' })
.catch(...catch_constraint('accounts_pkey', { id }, AlreadyExists))
guarantee proper updates & deletes (updated
)
Will throw is zero or more than one row had been updated.
var accounts = table(knex, 'accounts')
accounts()
.delete()
.then(updated)
var accounts = table(knex, 'accounts')
accounts()
.where('name', 'not found')
.update('name', 'Not Found')
.then(updated)
flow
We're providing built-in Flow type definitions.
license
MIT.
© Strider, 2016 — 2019.