summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* - spiff up autogenerate docs a bitMike Bayer2014-11-221-83/+138
|
* - add another test around something that is bugging/confusing me...Mike Bayer2014-11-221-0/+66
| | | | but i guess it's OK
* - fixesMike Bayer2014-11-226-35/+74
|
* tuple form as wellMike Bayer2014-11-221-1/+9
|
* - now that branching is an enormous chapter, break out the docs intoMike Bayer2014-11-228-1670/+1685
| | | | | individual pages. the pages here are a little slim in the middle but overall the one-page docs were getting extremely long.
* - add the refMike Bayer2014-11-221-0/+2
|
* - In conjunction with support for multiple independent bases, theMike Bayer2014-11-2211-168/+488
| | | | | | | | | | specific version directories are now also configurable to include multiple, user-defined directories. When multiple directories exist, the creation of a revision file with no down revision requires that the starting directory is indicated; the creation of subsequent revisions along that lineage will then automatically use that directory for new files. fixes #124
* - break out the concept of "down revision" into two pieces:Mike Bayer2014-11-224-49/+305
| | | | | | | | down_revision and "dependencies". For migration traversal, the downrevs we care about are the union of these two sets. however for location of nodes and branch labeling, we look only at down_revsion. this works really well and allows us to have mutually-dependent trees that can easily be itererated independently of each other. docs are needed
* - support the case where a mergepoint has a branchpoint immediatelyMike Bayer2014-11-222-40/+238
| | | | | | | | following it; this will be the norm in the case where parallel branches refer to each other as dependencies. this means we need to limit for from/to revisions based on current heads / ancestors of those heads whenever we merge/unmerge.
* - modernize the readme especially the SQLite thingMike Bayer2014-11-211-19/+20
|
* ModelOne now has unique constraints so require thatMike Bayer2014-11-211-0/+2
|
* - add more label syntaxesMike Bayer2014-11-211-0/+20
|
* - Added a rule for Postgresql to not render a "drop unique" and "drop index"Mike Bayer2014-11-215-0/+54
| | | | | | | | given the same name; for now it is assumed that the "index" is the implicit one Postgreql generates. Future integration with new SQLAlchemy 1.0 features will improve this to be more resilient. fixes #247
* include indexes in batchMike Bayer2014-11-215-49/+129
|
* - A change in the ordering when columns and constraints are dropped;Mike Bayer2014-11-213-69/+120
| | | | | | | autogenerate will now place the "drop constraint" calls *before* the "drop column" calls, so that columns involved in those constraints still exist when the constraint is dropped. fixes #247
* make the three way merge thing a separate section, we don't reallyMike Bayer2014-11-201-13/+16
| | | | even need it but should be fine
* - typoMike Bayer2014-11-201-2/+2
|
* put the sqlite thing near the top as it's the other big featureMike Bayer2014-11-201-30/+30
|
* - The "multiple heads / branches" feature has now landed. This isMike Bayer2014-11-2024-654/+4044
| | | | | | | | | | | | | | by far the most significant change Alembic has seen since its inception; while the workflow of most commands hasn't changed, and the format of version files and the ``alembic_version`` table are unchanged as well, a new suite of features opens up in the case where multiple version files refer to the same parent, or to the "base". Merging of branches, operating across distinct named heads, and multiple independent bases are now all supported. The feature incurs radical changes to the internals of versioning and traversal, and should be treated as "beta mode" for the next several subsequent releases within 0.7. fixes #167
* - changelog + some polishMike Bayer2014-11-203-13/+36
|
* Merge branch '242-config-vars' of https://bitbucket.org/nibrahim/alembic ↵Mike Bayer2014-11-202-2/+21
|\ | | | | | | into pr33
| * Adds tests for config_argsNoufal Ibrahim2014-11-201-0/+14
| |
| * Changes name of variable.Noufal Ibrahim2014-11-161-5/+5
| | | | | | | | | | This incorporates feedback from the package maintainer on the name of the variable.
| * Adds cfg_vars to Config.Noufal Ibrahim2014-11-161-2/+7
| | | | | | | | | | This dictionary can be used to pass key value pairs that are used as defaults while instantiating the SafeConfigParser.
* | The Oracle dialect sets "transactional DDL" to False by default,Mike Bayer2014-11-182-1/+8
| | | | | | | | | | as Oracle does not support transactional DDL. fixes #245
* | - Fixed a variety of issues surrounding rendering of Python code thatMike Bayer2014-11-166-67/+216
|/ | | | | | | | | | | contains unicode literals. The first is that the "quoted_name" construct that SQLAlchemy uses to represent table and column names as well as schema names does not ``repr()`` correctly on Py2K when the value contains unicode characters; therefore an explicit stringification is added to these. Additionally, SQL expressions such as server defaults were not being generated in a unicode-safe fashion leading to decode errors if server defaults contained non-ascii characters. fixes #243
* - reorganize tests that deal with running scriptsMike Bayer2014-11-105-173/+181
| | | | and reading scripts; try to put tests against common themes together, improve names
* - move the tests concerning #95 to test_versioning, which is currentlyMike Bayer2014-11-102-31/+43
| | | | where the tests focus on consumption of the versions/ directory.
* - changelog for pr bitbucket:29, fixes #174Mike Bayer2014-11-101-0/+10
|
* Merge branch 'add_column_with_index' of ↵Mike Bayer2014-11-102-0/+11
|\ | | | | | | https://bitbucket.org/davidszotten/alembic into pr29
| * Create index in add_column if requestedDavid Szotten2014-10-162-0/+11
| | | | | | | | Fixes #174
* | - editMike Bayer2014-11-101-2/+4
| |
* | - changelogbatch_alterMike Bayer2014-11-092-1/+31
| | | | | | | | fixes #21
* | - test fixupMike Bayer2014-11-095-60/+118
| | | | | | | | | | | | - get batch mode to fail gracefully, dropping the temp table if the operation fails - finish tutorial
* | - add a type here so that to account for pre-0.9 FK/type supportMike Bayer2014-11-091-1/+1
| |
* | Merge branch 'master' into batch_alterMike Bayer2014-11-091-7/+11
|\ \
| * | - adjust these to account for some MySQL deprecations regardingMike Bayer2014-11-091-7/+11
| | | | | | | | | | | | duplicate indexes against the same columns
* | | - add some connection cleanupMike Bayer2014-11-093-4/+10
| | |
* | | - more docsMike Bayer2014-11-081-7/+105
| | |
* | | documentingMike Bayer2014-11-081-9/+73
| | |
* | | - add a little step to get PG to work rudimentally, howeverMike Bayer2014-11-084-3/+29
| | | | | | | | | | | | | | | the drop + recreate routine still needs a solution for refernential integrity for it to be of general use
* | | - start docsMike Bayer2014-11-082-0/+62
| | | | | | | | | | | | | | | | | | | | | - run tests against mysql/PG to make sure auto mode works at least, try a proof of concept recreate for MySQL. recreate doesn't work on PG as constraint names are global (ugh). Will have to figure something out on that.
* | | - round trip testsMike Bayer2014-11-082-14/+157
| | | | | | | | | | | | - fixes to add column
* | | Merge branch 'master' into batch_alterMike Bayer2014-11-084-6/+88
|\ \ \ | |/ /
| * | - The :class:`~sqlalchemy.schema.Table` object is now returned whenMike Bayer2014-11-084-6/+88
| | | | | | | | | | | | | | | | | | | | | the :meth:`.Operations.create_table` method is used. This ``Table`` is suitable for use in subsequent SQL operations, in particular the :meth:`.Operations.bulk_insert` operation. fixes #205
* | | - finish up most featuresMike Bayer2014-11-083-67/+247
| | |
* | | move thisMike Bayer2014-11-081-2/+1
| | |
* | | - testing approaches for BatchOperationsImpl and ApplyBatchImplMike Bayer2014-11-082-30/+223
| | |
* | | proof of conceptMike Bayer2014-11-074-30/+292
| | |
* | | docstringMike Bayer2014-11-071-1/+65
| | |
View Lorry Controller Status