Support PostgreSQL version of Aurora Serverless

Some compatibility issues were brought up in #25 that show conflicts with the PostgreSQL version (likely because of sqlstring). There are also some additional data types (like structValue) that are only supported by the PostgreSQL version.

Overall, I think the two engines are rather interchangeable (thanks for that AWS). We likely need to add an engine config option or something similar since I don’t think the library can “auto detect” the underlying version.

I’ve created a new development branch (https://github.com/jeremydaly/data-api-client/tree/postgres-support) that should be the target of any pull requests regarding this. Please feel free to add comments to this issue with ideas or compatibility observations.

[jeremydaly]

Sorry for the late reply. This is likely due to the support for parametizing identifiers. I think full Postgres support will require a separate config flag.

[thchia]

I am happy to provide a fix for #25 . However, I think we need to deal with the fact that the maintainers of sqlstring will not be adding support for Postgres. Off the top of my head, there are a few options:

• Remove the dependency on sqlstring and rewrite the lone method this library currently uses (it’s small)
  • Pros: simple and clean
  • Cons: if we’re planning to make more use of sqlstring in the future, it will be harder
• Fork sqlstring and add Postgres support
  • Pros: can continue to rely on other features of sqlstring if we need them in the future
  • Cons: maintaining upstream changes can become unwieldy