-
Notifications
You must be signed in to change notification settings - Fork 26
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
Constructing catalogs #18
Comments
For what it's worth, |
I revised the dialect handling and there is no sensible way to start with an empty or 'default' catalog. Can you do the same thing starting with the ansi dialect catalog? If you can explain what you are doing in more detail I can help figure out how to do it or what deficiency in hssqlppp there is. The new dialect approach is a WIP. |
I've been building a library (see this and this to get a sense for what it will look like) on top of hssqlppp (which, by the way, is a wonderful and herculean enterprise - thanks for it!) that infers haskell types for queries and parameters. It will only support postgres for now, so I wanted to make sure the catalog updates are valid for postgres. ANSI catalog would suffice, but as far as I can tell, that's not exported either (nor is there a way to transform a dialect to catalog). |
Can you use something like 'diDefaultCatalog postgresDialect' to get the catalog? |
Ha, sorry, that should have been obvious. Thanks! |
I want to leave this bug open because I want to try to improve the documentation to make sure there is a guide about this and some examples. |
In version 0.4, one could construct a
Catalog
withemptyCatalog
ordefaultCatalog
, and a list of catalog updates. In 0.6,emptyCatalog
/defaultCatalog
seem to be gone, so it's unclear how to construct a catalog.The text was updated successfully, but these errors were encountered: