Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Change project prefix. | stuconnolly | 2012-09-26 | 1 | -101/+0 |
| | |||||
* | Add the ability for the client application to set the PostgreSQL application ↵ | stuconnolly | 2012-09-11 | 1 | -0/+2 |
| | | | | name when connecting. | ||||
* | Don't expose the handler protocol or libpq types to the client and remember ↵ | stuconnolly | 2012-09-07 | 1 | -2/+1 |
| | | | | to initailise type extensions when a connection is established. | ||||
* | Add a new connection error property. | stuconnolly | 2012-09-06 | 1 | -0/+2 |
| | |||||
* | PostgresKit: set the last error to be an instance of FLXPostgresError not a ↵ | stuconnolly | 2012-09-03 | 1 | -2/+3 |
| | | | | string. | ||||
* | Initial commit of PostgresKit, our new Postgres framework as a start towards ↵ | stuconnolly | 2012-09-03 | 1 | -0/+97 |
adding PostgreSQL support to Sequel Pro. Note, that the framerwork is by no means feature complete and in it's current state has quite a few limitations: - No support for Postgres' asynchronous query API - Only supports the very basic data types (char/text and numerics) - No support (outide of libpq) for re-establishing dropped connections Current feature support includes: - Basic connection handling - Query execution - Prepared statement execution - Encoding support similar to SPMySQL's |