-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support range types #164
Comments
I've been taking a stab at this, and can't seem to figure out where the "rules" for decoding a given message from Postgres wire format come from - @will any advice here? |
@miketheman It's in https://github.com/will/crystal-pg/blob/master/src/pg/decoder.cr Every postgres type has an ID, called (this is just from me fiddling with the library, I might be wrong) |
@asterite Thanks - I got that far. I'm more interested in how to interpret the bytes returned from PG. |
The functions in postgres are usually ending in Here is the range one I think: https://github.com/postgres/postgres/blob/b538c90b1bded5464787e2b8e4431302d24eb601/src/backend/utils/adt/rangetypes.c#L246 |
You can also call them as functions in postgres if that helps playing around with things faster:
|
This is an exploratory effort to support will#164 It is not ready for merging, but I wanted to to open it for discussion and review. Signed-off-by: Mike Fiedler <[email protected]>
This is an exploratory effort to support will#164 It is not ready for merging, but I wanted to to open it for discussion and review. Signed-off-by: Mike Fiedler <[email protected]>
I started a Draft PR for discussion. |
I can work on this, if it is stalled. |
Currently:
The text was updated successfully, but these errors were encountered: