Tudor Zaharia
Tudor Zaharia
Fixed in versions >= 0.3.2
H @esciullo is this still an issue with the 0.3.0 version?
Closing due to inactivity.
@thruflo Is this what you had in mind? ``` const result = useLiveQuery(`SELECT * FROM test WHERE id = ANY($1)`, [ [1, 2], ]) ``` Added a test: https://github.com/electric-sql/pglite/pull/548/files
`an alternative would be a {default: value} option (more explicit but also more verbose).` I think it's ok to be more verbose when you need that option. If we default...
`const items = results !== undefined ? results.rows : []` `const items = results?.rows ?? []`
If anyone is interested in pgcrypto for PGlite, please have a look at https://github.com/electric-sql/pglite/pull/834
From our docs: ``` There are two methods for querying the database, .query and .exec. The former supports parameters, while the latter supports multiple statements. ``` If those generated queries...
As a workaround, could someone try this or similar? ``` import { DataSource } from 'typeorm'; import { PGlite } from '@electric-sql/pglite'; const pgliteExec = await PGlite.create() pgliteExec.query = pgliteExec.exec...
> [@tdrz](https://github.com/tdrz) i'm not quite sure how reliable this is, since exec doesn't support params? Checked with `typeorm` maintainers, the migrations generally do not rely on parameters. Nevertheless, my suggestion...