phiresky

Results 120 issues of phiresky

since folder names contain literal backslashes ![image](https://user-images.githubusercontent.com/2303841/36668693-69016b42-1af2-11e8-8cae-88149c5f4d85.png)

I think it would be better to name the types more exactly like their pg counterparts e.g. ```typescript import {types as t} from '@hediet/typed-sql'; t.smallint t.integer t.bigint t.decimal t.numeric t.real...

```ts const id = 123; await db.single( sql .insertInto(a) .value({ id, foo: sql .from(bar) .where({ id }) .select(bar.x) .asExpression() }) ); ``` creates a query like ``` INSERT INTO roulette.games(id,...

This is caused by postgresql not knowing the type of values() with parameterized values. example: ```typescript const updateTmpTable = values(fromItemTypes(asset_classes, ["market_hash_name", "can_deposit", "coin_price"]), updateValues).as("temp"); const updateQuery = update(asset_classes).from(updateTmpTable) .where({ market_hash_name:...

`a.plus(b).cast(tInteger)` produces `a+b::integer` but it should produce `(a+b)::integer`

Currently errors are thrown as normal errors: `throw new Error("Expected at least one row.");` It would be good if they had some typed metadata that could be used as follows:...

I want to be able to do ```typescript export const tbl = s.table("tbl", { test: tInteger }); type Tbl = typeof tbl.$rowInstance; // instead of type Tbl = FromItemToOutRow; ```...

Like `.single()`, this should fail when the sql query does not return exactly zero rows. See for example [pg-promise](https://github.com/vitaly-t/pg-promise) `.none()`.

`a BETWEEN x AND y` `a.between(x, y)` is much easier to read than `a.isAtLeast(x).and(t.isAtMost(y))` https://www.postgresql.org/docs/9.1/static/functions-comparison.html