diff options
| author | Mike Bayer <mike_mp@zzzcomputing.com> | 2012-09-16 17:43:21 -0400 |
|---|---|---|
| committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2012-09-16 17:43:21 -0400 |
| commit | 6a3e993490ebedce39983a90ced3a87817e6d4ef (patch) | |
| tree | c798917198faa3ccf1a0dac9eb906fe63a28b389 /CHANGES | |
| parent | cbf747fdc4e4d6772090042ec357e315be2f61a4 (diff) | |
| download | sqlalchemy-6a3e993490ebedce39983a90ced3a87817e6d4ef.tar.gz | |
- genericize the test for ischema_names
- some fixes to the patch to handle empty args, whitespace
- changelog clarifies where this API fits at the moment
Diffstat (limited to 'CHANGES')
| -rw-r--r-- | CHANGES | 24 |
1 files changed, 24 insertions, 0 deletions
@@ -633,6 +633,30 @@ underneath "0.7.xx". The phrase is established using with_hint(). Courtesy Ryan Kelly [ticket:2506] + - [feature] The "ischema_names" dictionary of the + Postgresql dialect is "unofficially" customizable. + Meaning, new types such as PostGIS types can + be added into this dictionary, and the PG type + reflection code should be able to handle simple + types with variable numbers of arguments. + The functionality here is "unofficial" for + three reasons: + + 1. this is not an "official" API. Ideally + an "official" API would allow custom type-handling + callables at the dialect or global level + in a generic way. + 2. This is only implemented for the PG dialect, + in particular because PG has broad support + for custom types vs. other database backends. + A real API would be implemented at the + default dialect level. + 3. The reflection code here is only tested against + simple types and probably has issues with more + compositional types. + + patch courtesy Éric Lemoine. + - firebird - [feature] The "startswith()" operator renders as "STARTING WITH", "~startswith()" renders |
