sqlalchemy-commits — SVN commits logged to this list

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - The hostname-based connection format for SQL Server when using

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/4399431b53e5/
Changeset:   4399431b53e5
Branch:      None
User:        zzzeek
Date:        2014-09-03 16:31:29
Summary:     - The hostname-based connection format for SQL Server when using
pyodbc will no longer specify a default "driver name", and a warning
is emitted if this is missing.  The optimal driver name for SQL Server
changes frequently and is per-platform, so hostname based connections
need to specify this. DSN-based connections are preferred.
fixes #3182

Affected #:  5 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - lets start exampling this stuff

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/9494ca00d445/
Changeset:   9494ca00d445
Branch:      ticket_3100
User:        zzzeek
Date:        2014-09-03 01:46:55
Summary:     - lets start exampling this stuff

Affected #:  2 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

[Bitbucket <com...@bi...>]

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/7e0c22416270/
Changeset:   7e0c22416270
Branch:      None
User:        zzzeek
Date:        2014-09-02 21:05:32
Summary:     Merge branch 'master' into ticket_3100

Affected #:  84 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/ccfd26d96916/
Changeset:   ccfd26d96916
Branch:      ticket_3100
User:        zzzeek
Date:        2014-09-03 01:23:09
Summary:     - add options to get back pk defaults for inserts.
times spent start getting barely different...

Affected #:  2 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - default dialect, plus test against the default dialect...

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/613d8ca0f84d/
Changeset:   613d8ca0f84d
Branch:      None
User:        zzzeek
Date:        2014-09-02 21:04:12
Summary:     - default dialect, plus test against the default dialect...

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 3 new changesets

[Bitbucket <com...@bi...>]

3 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/ec840a6eea05/
Changeset:   ec840a6eea05
Branch:      None
User:        zzzeek
Date:        2014-09-02 20:18:09
Summary:     - An adjustment to table/index reflection such that if an index
reports a column that isn't found to be present in the table,
a warning is emitted and the column is skipped.  This can occur
for some special system column situations as has been observed
with Oracle. fixes #3180

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/da9e8be876fe/
Changeset:   da9e8be876fe
Branch:      None
User:        zzzeek
Date:        2014-09-02 20:24:33
Summary:     - backport the expects_warning() context manager from 1.0

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/34c0aaeedaf9/
Changeset:   34c0aaeedaf9
Branch:      rel_0_9
User:        zzzeek
Date:        2014-09-02 20:24:49
Summary:     - An adjustment to table/index reflection such that if an index
reports a column that isn't found to be present in the table,
a warning is emitted and the column is skipped.  This can occur
for some special system column situations as has been observed
with Oracle. fixes #3180

Affected #:  5 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: default dialect

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/9ee89dc88671/
Changeset:   9ee89dc88671
Branch:      None
User:        zzzeek
Date:        2014-09-02 19:39:16
Summary:     default dialect

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - add logic to compiler such that if stack is empty, we just

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/c0af2ee6c992/
Changeset:   c0af2ee6c992
Branch:      None
User:        zzzeek
Date:        2014-09-02 16:49:46
Summary:     - add logic to compiler such that if stack is empty, we just
stringify a _label_reference() as is.
- add .key to _label_reference(), so that when _make_proxy()
is called, we don't call str() on it anyway.
- add a test to exercise Query's behavior of adding all the order_by
expressions to the columns list of the select, assert that things
work out when we have a _label_reference there, that it gets sucked
into the columns list and spit out on the other side, it's referred
to appropriately, etc.   _label_reference() could theoretically
be resolved at the point we iterate _raw_columns() but
it's better to just let things work as they already do (except
nicer, since we get "tablename.colname" instead of just "somename"
 in the columns list) so that we aren't adding a ton of overhead
to _columns_plus_names in the common case.

Affected #:  5 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - reorganize

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/b621d232519b/
Changeset:   b621d232519b
Branch:      None
User:        zzzeek
Date:        2014-09-02 02:31:00
Summary:     - reorganize

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 4 new changesets

[Bitbucket <com...@bi...>]

4 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/ce0fee6993ee/
Changeset:   ce0fee6993ee
Branch:      None
User:        zzzeek
Date:        2014-09-02 00:23:19
Summary:     Merge branch 'master' into ticket_2992

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/3bffd139fe69/
Changeset:   3bffd139fe69
Branch:      None
User:        zzzeek
Date:        2014-09-02 01:26:15
Summary:     - this is all tests passing with new behavior + tests for warnings
in core/ORM + tests for order_by behavior

Affected #:  13 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/aa22eb9a4ffd/
Changeset:   aa22eb9a4ffd
Branch:      ticket_2992
User:        zzzeek
Date:        2014-09-02 02:13:18
Summary:     - changelog, migration

Affected #:  7 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/7c6a45c480a8/
Changeset:   7c6a45c480a8
Branch:      None
User:        zzzeek
Date:        2014-09-02 02:19:54
Summary:     - The :func:`~.expression.column` and :func:`~.expression.table`
constructs are now importable from the "from sqlalchemy" namespace,
just like every other Core construct.
- The implicit conversion of strings to :func:`.text` constructs
when passed to most builder methods of :func:`.select` as
well as :class:`.Query` now emits a warning with just the
plain string sent.   The textual conversion still proceeds normally,
however.  The only method that accepts a string without a warning
are the "label reference" methods like order_by(), group_by();
these functions will now at compile time attempt to resolve a single
string argument to a column or label expression present in the
selectable; if none is located, the expression still renders, but
you get the warning again. The rationale here is that the implicit
conversion from string to text is more unexpected than not these days,
and it is better that the user send more direction to the Core / ORM
when passing a raw string as to what direction should be taken.
Core/ORM tutorials have been updated to go more in depth as to how text
is handled.
fixes #2992

Affected #:  33 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 5 new changesets

[Bitbucket <com...@bi...>]

5 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/f09cd9d56d74/
Changeset:   f09cd9d56d74
Branch:      None
User:        zzzeek
Date:        2014-09-01 19:55:17
Summary:     - fix warning issue

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/f8ca3c8e3bed/
Changeset:   f8ca3c8e3bed
Branch:      None
User:        zzzeek
Date:        2014-09-01 20:03:10
Summary:     - approach the issue of "columns clause label" in a
type-based way to save on calls in columns_plus_names

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/1a8103a10bf1/
Changeset:   1a8103a10bf1
Branch:      ticket_2992
User:        zzzeek
Date:        2014-09-01 22:12:47
Summary:     - fix remaining ORM tests

Affected #:  6 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/382f82538b54/
Changeset:   382f82538b54
Branch:      None
User:        zzzeek
Date:        2014-09-01 23:20:49
Summary:     - more updates to text docs, literal_column, column etc.  in prep
for ticket 2992.

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/66bee3885554/
Changeset:   66bee3885554
Branch:      rel_0_9
User:        zzzeek
Date:        2014-09-01 23:21:33
Summary:     - more updates to text docs, literal_column, column etc.  in prep
for ticket 2992.

Affected #:  3 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 3 new changesets

[Bitbucket <com...@bi...>]

3 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/62d81c2ebdb6/
Changeset:   62d81c2ebdb6
Branch:      None
User:        zzzeek
Date:        2014-09-01 02:26:40
Summary:     - walk back these literal SQL lectures into something much more succinct.
the ORM one in particular was really long winded and I don't really care if people
use text() anyway, they'll figure it out ;)

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/c6998833755e/
Changeset:   c6998833755e
Branch:      ticket_2992
User:        zzzeek
Date:        2014-09-01 02:27:27
Summary:     Merge branch 'master' into ticket_2992

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/b2ebab0cd499/
Changeset:   b2ebab0cd499
Branch:      rel_0_9
User:        zzzeek
Date:        2014-09-01 02:27:38
Summary:     - walk back these literal SQL lectures into something much more succinct.
the ORM one in particular was really long winded and I don't really care if people
use text() anyway, they'll figure it out ;)

Affected #:  2 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

[Bitbucket <com...@bi...>]

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/12621ebea895/
Changeset:   12621ebea895
Branch:      None
User:        zzzeek
Date:        2014-09-01 00:06:11
Summary:     Merge branch 'master' into ticket_2992

Affected #:  22 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/c5d4762ecdac/
Changeset:   c5d4762ecdac
Branch:      ticket_2992
User:        zzzeek
Date:        2014-09-01 02:00:22
Summary:     - add column(), table() to the base API.  these are used like crazy,
I use them constantly, and the new textual warnings recommend them
- use very specific, contextual warnings for text/column/literal_column/table
requested.
- when interpreting columns, use heuristics to decide if the expr
is column() or literal_column().  definitely warn that we'd rather
not do this.  Be lenient about '*', numbers for now.
- get all tests in test/sql/ to work again

Affected #:  13 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

[Bitbucket <com...@bi...>]

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/1b3e3d915597/
Changeset:   1b3e3d915597
Branch:      rel_0_9
User:        zzzeek
Date:        2014-09-01 00:05:17
Summary:     - improve from_statement() doc

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/bdfe680708d8/
Changeset:   bdfe680708d8
Branch:      None
User:        zzzeek
Date:        2014-09-01 00:05:31
Summary:     - improve from_statement() doc

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 3 new changesets

[Bitbucket <com...@bi...>]

3 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/e42ced2ecac0/
Changeset:   e42ced2ecac0
Branch:      None
User:        zzzeek
Date:        2014-09-01 00:00:34
Summary:     - these tests were squashing deprecation warnings all along...

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/197233152882/
Changeset:   197233152882
Branch:      None
User:        zzzeek
Date:        2014-09-01 00:00:49
Summary:     - refine this a bit to better check for exception type

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/d7131ffad378/
Changeset:   d7131ffad378
Branch:      None
User:        zzzeek
Date:        2014-09-01 00:02:24
Summary:     - optional 'b' here for py3k

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

[Bitbucket <com...@bi...>]

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/903b0a42e71c/
Changeset:   903b0a42e71c
Branch:      None
User:        zzzeek
Date:        2014-08-31 21:21:42
Summary:     - updated callcounts

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/3c60d3b1ca49/
Changeset:   3c60d3b1ca49
Branch:      None
User:        zzzeek
Date:        2014-08-31 21:22:00
Summary:     - A new style of warning can be emitted which will "filter" up to
N occurrences of a parameterized string.   This allows parameterized
warnings that can refer to their arguments to be delivered a fixed
number of times until allowing Python warning filters to squelch them,
and prevents memory from growing unbounded within Python's
warning registries.
fixes #3178

Affected #:  17 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

[Bitbucket <com...@bi...>]

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/e39cac10ba0d/
Changeset:   e39cac10ba0d
Branch:      rel_0_9
User:        zzzeek
Date:        2014-08-31 17:44:51
Summary:     - start encouraging the use of text() for injection of string-based SQL
rather than straight strings.  reference #2992

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/7e417665d252/
Changeset:   7e417665d252
Branch:      None
User:        zzzeek
Date:        2014-08-31 17:45:20
Summary:     - start encouraging the use of text() for injection of string-based SQL
rather than straight strings.  reference #2992

Affected #:  2 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - warn for _literal_as_text receiving string

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/5b0ac2748004/
Changeset:   5b0ac2748004
Branch:      ticket_2992
User:        zzzeek
Date:        2014-08-31 02:55:52
Summary:     - warn for _literal_as_text receiving string
- create new label reference construct, applies to order_by, group_by,
distinct, asc/desc

Affected #:  5 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - alter the yield_per eager restriction such that joined many-to-one loads

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/f995a63d6c0b/
Changeset:   f995a63d6c0b
Branch:      None
User:        zzzeek
Date:        2014-08-30 21:45:50
Summary:     - alter the yield_per eager restriction such that joined many-to-one loads
are still OK, since these should be fine.

Affected #:  5 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - continue moving things out that don't need to be there

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/0bd074cc5ae9/
Changeset:   0bd074cc5ae9
Branch:      None
User:        zzzeek
Date:        2014-08-30 08:35:35
Summary:     - continue moving things out that don't need to be there
- an existing state shouldn't need its load_options/load_path updated;
it should maintain those from its original Query source.  there's no
tests that check this behavior

Affected #:  2 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - clean up zoomark a little and try to get new profiles written

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/51c7005dc5cc/
Changeset:   51c7005dc5cc
Branch:      None
User:        zzzeek
Date:        2014-08-30 06:11:32
Summary:     - clean up zoomark a little and try to get new profiles written

Affected #:  4 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - do the polymorphic thing as a decorator so it's out of the way otherwise

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/04f0e11051f0/
Changeset:   04f0e11051f0
Branch:      None
User:        zzzeek
Date:        2014-08-30 02:10:54
Summary:     - do the polymorphic thing as a decorator so it's out of the way otherwise

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - bump callcounts down

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/a52f84d4d841/
Changeset:   a52f84d4d841
Branch:      None
User:        zzzeek
Date:        2014-08-30 01:16:29
Summary:     - bump callcounts down

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 3 new changesets

[Bitbucket <com...@bi...>]

3 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/e695138cb4c9/
Changeset:   e695138cb4c9
Branch:      None
User:        zzzeek
Date:        2014-08-29 22:57:12
Summary:     - further move things vertically, at which point things are inlined enough
that I'd like to start de-inlining again in the hopes of making this readable.

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/ab5a1a7f4a87/
Changeset:   ab5a1a7f4a87
Branch:      master
User:        zzzeek
Date:        2014-08-29 23:46:57
Summary:     - pull out populators back into separate functions, though still very inlined

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/5eff49e08d54/
Changeset:   5eff49e08d54
Branch:      attempt_c_loading
User:        zzzeek
Date:        2014-08-30 01:07:27
Summary:     - attempt to write part of _populate_full in C.  Performance difference
is pretty much zippo!  1%.  to use C code here would require a much more
fundamental rewrite of everything so that we aren't just calling python
functions.

Affected #:  3 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 3 new changesets

[Bitbucket <com...@bi...>]

3 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/5686472f4246/
Changeset:   5686472f4246
Branch:      None
User:        zzzeek
Date:        2014-08-29 22:28:19
Summary:     - defaultdict benchmarks faster than a namedtuple; OK
- inline the column-based expiration operations as well

Affected #:  4 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/8155138e0aac/
Changeset:   8155138e0aac
Branch:      None
User:        zzzeek
Date:        2014-08-29 22:29:46
Summary:     - use default dialect for compile test here

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/41a3e1fd99f6/
Changeset:   41a3e1fd99f6
Branch:      None
User:        zzzeek
Date:        2014-08-29 22:32:08
Summary:     - need to use safe_discard() at least in _restore_snapshot(), let's use it
everywhere in Session since the optimized one only applies to loading

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 3 new changesets

[Bitbucket <com...@bi...>]

3 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/8c8b22e4742d/
Changeset:   8c8b22e4742d
Branch:      rel_0_9
User:        zzzeek
Date:        2014-08-29 20:23:36
Summary:     - add a test to events within load to verify something we want
to ensure stays the same on 1.0

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/b9046a163bd9/
Changeset:   b9046a163bd9
Branch:      None
User:        zzzeek
Date:        2014-08-29 20:25:09
Summary:     - re-establish and test some behavior from previous versions, that
if a load() or refresh() event changes history (which...why...but anyway)
the state of the object is the same; currently it seems that history
gets reset but on a refresh, the object still goes into session.dirty
- simplify what we store in partials

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/9449c102768e/
Changeset:   9449c102768e
Branch:      None
User:        zzzeek
Date:        2014-08-29 21:07:11
Summary:     - reorganize how create_row_processor() communicates up to
instances(), using a named tuple it can assign to directly.  this way
we never have to worry about that structure changing anymore, though
we are still having it append (key, fn) which is kind of awkward.
- inline _populators() into instance(), it's a little verbose but
saves an fn call

Affected #:  3 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.