eXecuteye
DTDrizzle Team
•Created by eXecuteye on 7/29/2024 in #help
allow passing undefined to limit
The 0.32.1 release (https://github.com/drizzle-team/drizzle-orm/releases/tag/0.32.1) added support for limit 0 in all dialects...
However, in some cases i used "0" as a fallback for "do not apply limit" (as if limit was undefined, which is not allowed currently)
Pointed out as workaround in this issue: https://github.com/drizzle-team/drizzle-orm/issues/728#issuecomment-1581806431
Is there some other way to define the
.limit(limitNum)
where limit is only applied if limit is defined?
Can we allow undefined to be passed to limit() to not apply it?1 replies
DTDrizzle Team
•Created by eXecuteye on 6/20/2024 in #help
drizzle postgis geometry always geometry(point)
Hello, i am currently testing out the basic postGis support and it would be nice if i can get it working as desired...
Basically i want point/pointZ and linestring/linestringZ...
The 0.31.0 release added
geometry from the PostgreSQL PostGIS extension
, however, as indicated it currently only supports type: "point"
. But the release also states, that we can specify any other string to use some other type...
i was wondering what steps are necessary to get eg: linestring to work?
point: geometry("point", { type: "point" }),
or point: geometry("point", { type: "pointZ" }),
results in:
on drizzle-kit generate
with linestring i tried:
linestring: geometry("linestring", { type: "linestring" })
or linestring: geometry("linestring", { type: "linestringZ" })
resulting in:
on drizzle-kit generate
the only way to get around this issue that i am currently aware is just manually swap out the geometry(point)
with geometry(linestring)
in the generated sql and then migrate...4 replies
DTDrizzle Team
•Created by eXecuteye on 6/17/2024 in #help
drizzle-kit generate not working with unhelpful error message
Ian into an issue with generate yesterday and can't really make sense of the error...
Downgrading drizzle-orm or drizzle-kit version does not change anything (min version tried: orm: 32.0 and kit:22.0 -> (did not go lower because since v32 the new drizzle kit version was required and a drizzle-kit up was done and the config changes were applied, etc...))
I dont know if any change in my schemas causes this issue but the schemas seem correct to me... Because i don't know what causes this looking at the error message i have a hard time debugging this...
Did you run into the same issue or was yours of different nature?
2 replies