double precision | No build context available
mirkadev opened this issue Β· comments
Vladimir Mironov commented
Describe the bug
Got the No build context available
error after running migrations
QueryFailedError: No build context available
π₯ This is a nasty error, which was unexpected by pg-mem. Also known "a bug" π Please file an issue !
*οΈβ£ Failed SQL statement: ALTER TABLE "synchronization_data" ALTER COLUMN value TYPE double precision;
To Reproduce
CREATE TABLE "synchronization_data" ("id" SERIAL NOT NULL, "synchronizationId" integer NOT NULL, "name" character varying NOT NULL, "value" integer NOT NULL);
ALTER TABLE "synchronization_data" ALTER COLUMN value TYPE double precision;
pg-mem version
cat ./node_modules/pg-mem/package.json | grep version
"version": "2.6.12",
"description": "A memory version of postgres",
"release-deno": "git add -A && git commit -m \"Build deno [autogenerated commit]\" && PACKAGE_VERSION=$(cat package.json | grep \\\"version\\\" | head -1 | awk -F: '{ print $2 }' | sed 's/[\",]//g' | tr -d '[[:space:]]') && git tag $PACKAGE_VERSION && git push --tags",