| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
on get_table_names(). [ticket:1739]
|
|
|
|
| |
- a lot of these drivers suck at decimals, not sure what to do
|
|
|
|
|
|
|
| |
mysql dialects.
- added an explicit test for [ticket:1216]
- some questions remain about MSSQL - would like to simplify/remove bind handling for numerics
|
|
|
|
| |
[ticket:1738]
|
| |
|
|
|
|
|
|
| |
case-sensitive column name during reflect and add
"quote=True" to the generated Column, so that proper
quoting is maintained.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
have native boolean support, will generate a CHECK
constraint "col IN (0, 1)" along with the int/smallint-
based column type. This can be switched off if
desired with create_constraint=False.
Note that MySQL has no native boolean *or* CHECK constraint
support so this feature isn't available on that platform.
[ticket:1589]
|
|
|
|
|
|
|
|
|
|
| |
types to more intelligently determine float() vs. Decimal(),
[ticket:1567]
- since result processing is a hot issue of late, the DBAPI type
returned from cursor.description is certainly useful in cases like
these to determine an efficient result processor. There's likely
other result processors that can make use of it. But, backwards
incompat change to result_processor(). Happy major version number..
|
|
|
|
|
|
| |
generate "START WITH" and "INCREMENT BY" by default,
on Oracle and Postgresql. Firebird doesn't support
these keywords right now. [ticket:1545]
|
| |
|
|
|
|
|
| |
or explicit sequence-stated schema, into account.
[ticket:1576]
|
| |
|
| |
|
|
|
|
|
|
|
| |
of this object has been simplified and moved into
ExecutionContext. Dialects which support sequences should
add a `fire_sequence()` method to their execution context
implementation. [ticket:1566]
|
|
|
|
| |
TEXT, INET, ..."
|
| |
|
|
|
|
|
|
| |
adds a __nonzero__ to _BinaryExpression to avoid faulty comparisons during hash
collisions (which only occur on Jython)
fixes #1547
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Several keywords were missing, and various words were wrongly included
in the set. I took the current list of keywords out of "keywords.cpp", filtering
out effective reserverd words with a simple script that created a dummy table
with a field named after each word.
While this fixes a few tests (for example, those creating a table with a "start"
field, a Firebird reserverd words not previously registered as such), it may
introduce a backward incompatibility with previous SA releases: should this be
not wanted, I will add previous non-reserved-words to the set.
|
| |
|
|
|
|
| |
field length
|
| |
|
| |
|
|
|