summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy
Commit message (Collapse)AuthorAgeFilesLines
* - *Major* cleanup / modernization of the InformixMike Bayer2010-10-013-76/+259
| | | | | dialect for 0.6, courtesy Florian Apolloner. [ticket:1906]
* - Fixed bug in query.update() where 'evaluate' or 'fetch'Mike Bayer2010-10-012-3/+9
| | | | | | expiration would fail if the column expression key was a class attribute with a different keyname as the actual column name. [ticket:1935]
* - add additional logic that duplicates mapper's prop.copy(); ↵Mike Bayer2010-10-012-6/+23
| | | | | | | | | prop.columns.append(col) logic when columns are present in a joined subclass with an attribute name different than the column name itself [ticket:1931] - add coverage to verify that we need to check (obj.name or name) when deciding if a Column from a mixin should be added to the mapped table
* - reworked the internals of mapper.cascade_iterator() toMike Bayer2010-10-013-17/+35
| | | | | cut down method calls by about 9% in some circumstances. [ticket:1932]
* py2.4 didn't seem to like super() on an exceptionMike Bayer2010-09-291-1/+1
|
* don't need itertools hereMike Bayer2010-09-291-8/+6
|
* - CircularDependencyError now has .cycles and .edgesMike Bayer2010-09-292-14/+18
| | | | | | members, which are the set of elements involved in one or more cycles, and the set of edges as 2-tuples. [ticket:1890]
* - Fixed bug whereby columns on a mixin wouldn't propagateMike Bayer2010-09-282-4/+7
| | | | | | | correctly to a single-table inheritance scheme where the attribute name is different than that of the column. [ticket:1930]. Note [ticket:1931] which is the same issue for joined inh, not yet resolved.
* @mapperproperty -> @declared_attrMike Bayer2010-09-272-32/+32
|
* - @classproperty 's official name/location for usageMike Bayer2010-09-252-38/+91
| | | | | | | with declarative is sqlalchemy.ext.declarative.mapperproperty. Same thing, but moving there since it is more of a "marker" that's specific to declararative, not just an attribute technique. [ticket:1915]
* - Fixed recursion overflow which could occur when operatingMike Bayer2010-09-251-1/+1
| | | | | with two expressions both of type "NullType", but not the singleton NULLTYPE instance. [ticket:1907]
* - fix a typo that was apparently not really impacting anythingMike Bayer2010-09-251-1/+1
|
* fix the default hereMike Bayer2010-09-251-1/+1
|
* make less ficticious ;-)Chris Withers2010-09-241-2/+2
|
* doc editsMike Bayer2010-09-231-3/+4
|
* doc editsMike Bayer2010-09-223-19/+26
|
* - in depth docs about some merge() tipsMike Bayer2010-09-224-3/+25
| | | | | | | | | | | | - docs about backref cascade - Another new flag on relationship(), cascade_backrefs, disables the "save-update" cascade when the event was initiated on the "reverse" side of a bidirectional relationship. This is a cleaner behavior so that many-to-ones can be set on a transient object without it getting sucked into the child object's session, while still allowing the forward collection to cascade. We *might* default this to False in 0.7.
* - Query.select_from() has been beefed up to helpMike Bayer2010-09-211-13/+19
| | | | | | | | ensure that a subsequent call to query.join() will use the select_from() entity, assuming it's a mapped entity and not a plain selectable, as the default "left" side, not the first entity in the Query object's list of entities.
* - the logging message emitted by the engine whenMike Bayer2010-09-211-1/+1
| | | | | a connection is first used is now "BEGIN (implicit)" to emphasize that DBAPI has no explicit begin().
* - Patched a case where query.join() would adapt theMike Bayer2010-09-212-6/+39
| | | | | right side to the right side of the left's join inappropriately [ticket:1925]
* - scoped_session emits a warning when configure() isMike Bayer2010-09-211-2/+9
| | | | | called if a Session is already present (checks only the current thread) [ticket:1924]
* - @classproperty (soon/now @mapperproperty) takes effect forMike Bayer2010-09-201-43/+55
| | | | | | __mapper_args__, __table_args__, __tablename__ on a base class that is not a mixin, as well as mixins. [ticket:1922]
* - as_scalar(), label() can be called on a selectableMike Bayer2010-09-181-3/+10
| | | | | which contains a Column that is not yet named. [ticket:1862]
* - An informative error message is raised if a ColumnMike Bayer2010-09-183-9/+19
| | | | | | | | | which has not yet been assigned a name, i.e. as in declarative, is used in a context where it is exported to the columns collection of an enclosing select() construct, or if any construct involving that column is compiled before its name is assigned. [ticket:1862]
* add oursql to has lastrowidMike Bayer2010-09-181-1/+1
|
* - use "key in dict" rather than KeyError if the usual caseMike Bayer2010-09-181-37/+28
| | | | | | | | is that the key is not present. - don't need to uniquify Index schemes, just don't copy Indexes that were known to be generated from the index=True flag - user facing changes go in CHANGES - Table.c allows string lookup
* mergeChris Withers2010-09-168-27/+72
|\
| * - Fixed a regression in 0.6.4 whereby the change thatMike Bayer2010-09-162-3/+9
| | | | | | | | | | | | | | | | allowed cursor errors to be raised consistently broke the result.lastrowid accessor. Test coverage has been added for result.lastrowid. Note that lastrowid is only supported by Pysqlite and some MySQL drivers, so isn't super-useful in the general case.
| * - fix test_single test to use default dialectMike Bayer2010-09-154-20/+44
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - The exception raised by Session when it is used subsequent to a subtransaction rollback (which is what happens when a flush fails in autocommit=False mode) has now been reworded (this is the "inactive due to a rollback in a subtransaction" message). In particular, if the rollback was due to an exception during flush(), the message states this is the case, and reiterates the string form of the original exception that occurred during flush. If the session is closed due to explicit usage of subtransactions (not very common), the message just states this is the case. - The exception raised by Mapper when repeated requests to its initialization are made after initialization already failed no longer assumes the "hasattr" case, since there's other scenarios in which this message gets emitted, and the message also does not compound onto itself multiple times - you get the same message for each attempt at usage. The misnomer "compiles" is being traded out for "initialize".
| * - Fixed a regression in 0.6.5 which occurred if youMike Bayer2010-09-151-1/+1
| | | | | | | | | | passed an empty list to "include_properties" on mapper() [ticket:1918]
| * - add message to documentation stating that collection validators cannotMike Bayer2010-09-151-0/+5
| | | | | | | | load the collection being validated. [ticket:1916]
| * - Fixed bug that would prevent "subqueryload" fromMike Bayer2010-09-132-3/+13
| | | | | | | | | | | | | | | | | | | | | | | | working correctly with single table inheritance for a relationship from a subclass - the "where type in (x, y, z)" only gets placed on the inside, instead of repeatedly. - When using from_self() with single table inheritance, the "where type in (x, y, z)" is placed on the outside of the query only, instead of repeatedly. May make some more adjustments to this.
* | add warning about dodgy use of tometadataChris Withers2010-09-161-1/+5
| |
* | tometadata now copies indexes as wellChris Withers2010-09-161-1/+22
| |
* | make sure kwargs are copied by tometadataChris Withers2010-09-161-1/+1
|/
* - Fixed recursion bug which could occur when movingMike Bayer2010-09-133-9/+9
| | | | | | | an object from one reference to another, with backrefs involved, where the initiating parent was a subclass (with its own mapper) of the previous parent.
* more docs on thisMike Bayer2010-09-122-13/+17
|
* need this tooMike Bayer2010-09-121-0/+2
|
* - lazy loads for relationship attributes now useMike Bayer2010-09-129-59/+130
| | | | | | | | | | | | | | | | | | | | | the current state, not the "committed" state, of foreign and primary key attributes when issuing SQL, if a flush is not in process. Previously, only the database-committed state would be used. In particular, this would cause a many-to-one get()-on-lazyload operation to fail, as autoflush is not triggered on these loads when the attributes are determined and the "committed" state may not be available. [ticket:1910] - A new flag on relationship(), load_on_pending, allows the lazy loader to fire off on pending objects without a flush taking place, as well as a transient object that's been manually "attached" to the session. Note that this flag blocks attribute events from taking place when an object is loaded, so backrefs aren't available until after a flush. The flag is only intended for very specific use cases.
* - Slight improvement to the behavior of "passive_updates=False"Mike Bayer2010-09-122-5/+12
| | | | | | | | | | | when placed only on the many-to-one side of a relationship; documentation has been clarified that passive_updates=False should really be on the one-to-many side. - Placing passive_deletes=True on a many-to-one emits a warning, since you probably intended to put it on the one-to-many side.
* - collection docsMike Bayer2010-09-093-5/+14
| | | | | | | | - Added an assertion during flush which ensures that no NULL-holding identity keys were generated on "newly persistent" objects. This can occur when user defined code inadvertently triggers flushes on not-fully-loaded objects.
* - add doc pages for exceptionsMike Bayer2010-09-092-3/+3
|
* doc editsMike Bayer2010-09-081-13/+23
|
* editsMike Bayer2010-09-082-13/+13
|
* - Applied patches from [ticket:1904] to getrel_0_6_4Mike Bayer2010-09-072-22/+16
| | | | | | basic Informix functionality up again. We rely upon end-user testing to ensure that Informix is working to some degree.
* - Added a mutex to the identity map which mutexesMike Bayer2010-09-071-28/+49
| | | | | | | | remove operations against iteration methods, which now pre-buffer before returning an iterable. This because asyncrhonous gc can remove items via the gc thread at any time. [ticket:1891]
* - pending deprecation in 0.7 for the execute/scalar on clauseelementMike Bayer2010-09-073-9/+11
|
* - Fixed FB bug whereby a column default would fail toMike Bayer2010-09-061-1/+2
| | | | reflect if the "default" keyword were lower case.
* unify query.with_parent, util.with_parent, fix docs some moreMike Bayer2010-09-062-50/+46
|
* doc updatesMike Bayer2010-09-064-10/+58
|
View Lorry Controller Status