Hey folks -
Building on the great success of 0.9.5 just a few hours ago today, 0.9.6
is out! One of the changes in 0.9.5 had more of an impact than
expected and I determined it was better just reverting this particular
change, as there's a much better solution to it on deck for version 1.0
-
SQLAlchemy release 1.0.1 is now available.
This is a quick bug-fix release that repairs several new regressions
identified in the 1.0.0 release, not found during the beta period. All
users of 1.0.0 are encouraged to upgrade to 1.0.1.
Key elements of this release include fixes regarding the
On 5/3/15 3:44 PM, Walter King wrote:
We've been using branching for a bit and it mostly works the way we
want. Twice now we've run into the error when upgrading heads:
AssertionError: Can't do an UPDATE because downrevision is ambiguous
The policy we've had is when you create a new
SQLAlchemy release 1.0.4 is now available.
With release 1.0.4 we are pretty much through all the bumps we had in
the 0.9 to 1.0 movement. Four additional very minor regressions are
solved in this release. Most prominently, another issue regarding recent
enhancements to the
Alembic release 0.7.6 is now available.
This release has a few bug fixes in the new batch mode as well as one
in the new branching model, which otherwise has gone amazingly well
considering how complicated it was to implement.
Also a couple of new features to help with custom types and with
Hello list !
It is my great pleasure to announce that SQLAlchemy release 1.0.0 is now
available.
Release 1.0.0 marks the tenth major SQLAlchemy series and occurs within
the tenth year of the SQLAlchemy project overall; development started in
2005 and the release of 0.1.0 was in February of
SQLAlchemy release 1.0.6 is now available.
This release includes a handful of new bugfixes and some small feature
adds, pushed along by a high level of community involvement.
The most critical issue fixed involves the versioning feature of the
ORM, where the version counter of a row could be
On 6/26/15 12:23 PM, Jonathon Nelson wrote:
Greetings!
I am trying to use alembic to drop and re-create a PL/pgSQL function,
and the function has embedded percentile (for use in RAISE but also
present in comments, etc...).
When rendering the upgrade as an 'offline' sql upgrade script, the
On 6/26/15 12:49 PM, Mike Bayer wrote:
On 6/26/15 12:23 PM, Jonathon Nelson wrote:
Greetings!
I am trying to use alembic to drop and re-create a PL/pgSQL function,
and the function has embedded percentile (for use in RAISE but also
present in comments, etc...).
When rendering
On 5/31/15 7:00 PM, Wavemaker wrote:
Well, upon digging further myself, I noticed that was an old foreign
key in my Pictures table referring to the non-existant auth_user table:
sql: last_changed_user_id integer NOT NULL REFERENCES
auth_user (id)
This was not referenced anymore in the
On 5/29/15 6:36 PM, Wavemaker wrote:
Hello All,
I'm trying to use Alembic for versioning my Camelot
(http://www.python-camelot.com) schema, which is essentially
sqlalchemy on the database side. When using autogenerate I get a
NoSuchTableError. The odd thing is that I get this error for a
On 5/22/15 2:18 PM, Sylvain Martel wrote:
Hi, I tested this and while the firebird error message is now gone,
I am getting this error:
Error while preparing SQL statement:)
sqlalchemy.exc.DatabaseError: (fdb.fbcore.DatabaseError) ('Error while
preparing SQL statement:\n- SQLCODE:
On 5/26/15 9:47 AM, Sylvain Martel wrote:
Hi,
Not knowing much about SQL stuff, I used Flask-Migrate, which use
alembic, to deal with migrations. But now I have to deal with a
migration where I can't simply destroy the SQLite database and remake
it.(which is how I dealt so far when an
On 8/1/15 6:59 PM, Ian McCullough wrote:
I've been getting up to speed with SQLAlchemy and alembic and having a
great time of it. This is some great stuff!
One thing that's been confounding me is this: My Alembic schema
revisions are 'authoritative' for my metadata (i.e. I've started from
Hi list -
Alembic 0.8.0 is now available.
This release includes a large series of reorganizations in order to
provide several new extension APIs which dramatically increase the
degree to which Alembic can be extended.
The average Alembic environment should hopefully not notice anything
Hi Paweł -
this is fixed in master and the rel_0_7 branch. I should be releasing
today.
- mike
On 7/22/15 6:10 AM, Paweł Piotr Przeradowski wrote:
Hi,
Thanks for reply. It completes with correct results. I am gonna send
you a stripped version of scrips in a private message.
Pawel.
Alembic 0.7.7 is now available.
This is a bugfix release sent out ahead of the very soon to release 0.8
version, which features major new public APIs involving extensibility of
operations and autogeneration.
Most critical in this fix is a recently discovered CPU-intensive
situation which
SQLAlchemy release 0.9.10 is now available.
This is a maintenance release of the 0.9 series, delivering an array of
bug fixes and small feature enhancements which typically have been
backported from the 1.0 series. As the 1.0 series has been in production
use for some months now, the 0.9
SQLAlchemy release 1.0.8 is now available.
Release 1.0.8 comes almost immediately after 1.0.7, as a new issue
involving the connection pool has been identified and fixed which
impacts any application that relies upon consistent behavior of the
.info dictionary on a connection that is
On 7/13/15 12:46 AM, Mikko Ohtamaa wrote:
Hi,
I am trying to use Alembic in a way that the codebase is split to
several Python packages and each package tracks their own tables and
migration history independently. Effective each package has its own
versions and env.py. Is this possible? I
SQLAlchemy release 1.0.7 is now available.
This release contains a series of regression fixes, some additional
bugfixes, and a few new Core level features, including a new .cast()
method available on column constructs as well as support for many new
keywords used in creating sequences.
Next
On 10/29/15 4:26 PM, Gastón Avila wrote:
> Hi all,
>
> I used alembic to generate (auto) a migration which added a table to my
> postgresql DB which had a foreign key constraint matching two columns in
> the new table to two columns in an existing one. The two columns in the
> existing table
On 11/08/2015 05:42 AM, Ofir Herzas wrote:
> Changing a VARCHAR column to CLOB (TEXT) raises the following exception
> under Oracle:
>
> |
> sqlalchemy.exc.DatabaseError:(cx_Oracle.DatabaseError)ORA-22858:invalid
> alteration of datatype
> [SQL:'ALTER TABLE tab MODIFY col CLOB']
>
> |
>
>
I'd take a look at
http://alembic.readthedocs.org/en/latest/api/operations.html#operation-plugins
and for a longer example
http://alembic.readthedocs.org/en/latest/cookbook.html#replaceable-objects.
On 11/11/2015 04:26 PM, Alyssa Kwan wrote:
> Hi all,
>
> I have a single logical Alembic
we just had nearly the identical problem here where we hit the bizarre
fact that LIMIT won't work in the correlated subquery, and we went with
a temp table.
On 11/07/2015 02:27 PM, vitaly numenta wrote:
> Thank you Michael. I was hoping to do it the native sqlalchemy way,
> because my function
this was kind of a big issue so that is fixed and in 0.8.3. today.
On 10/16/15 10:36 AM, Mike Bayer wrote:
> this is a bug,
> https://bitbucket.org/zzzeek/alembic/issues/333/batch-fails-on-tables-that-have-indexes
> is added. thanks for reporting!
>
>
>
> On 10/16/15 4
SQLAlchemy release 1.0.9 is now available.
Release 1.0.9 is a bugfix release, pushing out a collection of mostly
small fixes that have accumulated over the past few months. In
particular there is one small but important fix for users of the latest
cx_Oracle library (5.2 or greater) in
On 10/14/15 12:41 AM, Fayaz Yusuf Khan wrote:
> Hi,
> Looks like the autogen_context parameter has changed type recently.
indeed it has:
http://alembic.readthedocs.org/en/latest/api/autogenerate.html#alembic.autogenerate.api.AutogenContext
>
> I'm getting this exception:
>
> Traceback
see the version_table_schema parameter :
http://alembic.readthedocs.org/en/latest/api/runtime.html?highlight=version_table_schema#alembic.runtime.environment.EnvironmentContext.configure.params.version_table_schema
On 10/9/15 9:30 AM, wwwald wrote:
> Hi,
>
> Sorry if this is basic - I just
On 11/12/2015 11:46 AM, Alyssa Kwan wrote:
> Thanks, Michael!
>
> In terms of the ReplaceableObject, I was hoping for a composite
> operation that could use existing Alembic operations, without needing to
> generate the underlying SQL.
For instance, the single composite
> operation would
On 8/29/15 7:13 AM, Martin Marrese wrote:
On Fri, Aug 28, 2015 at 8:16 PM, ma...@tokbox.com
mailto:ma...@tokbox.com wrote:
Hi,
I am trying to generate sql scripts in offline mode. But when
executing the delete in the following manner:
op.execute(
On 9/2/15 3:13 AM, Fayaz Yusuf Khan wrote:
Hi,
I'm seeing this weird issue where several global variables in env.py
are set as null when accessed from render_item.
Code: env.py
def render_item(type_, obj, autogen_context):
print globals()
I'm not deeply familiar with the vagaries of
On 9/22/15 7:38 PM, Sergi Pons Freixes wrote:
2015-09-22 16:24 GMT-07:00 Mike Bayer <mike...@zzzcomputing.com
<mailto:mike...@zzzcomputing.com>>:
Revision runs fine, but now when I run the upgrade it does not
find the alembic_version table (attached logs).
On 9/22/15 2:25 PM, Sergi Pons Freixes wrote:
2015-09-22 10:44 GMT-07:00 Mike Bayer <mike...@zzzcomputing.com
<mailto:mike...@zzzcomputing.com>>:
On 9/22/15 1:41 PM, Sergi Pons Freixes wrote:
Additional update: If on the env.py I substitute "__table_args
On 9/21/15 6:09 PM, Sergi Pons Freixes wrote:
2015-09-21 14:18 GMT-07:00 Mike Bayer <mike...@zzzcomputing.com
<mailto:mike...@zzzcomputing.com>>:
OK, I'm still not able to reproduce (see attached), as long as
include_schemas=True. However, in your env.
On 9/22/15 1:41 PM, Sergi Pons Freixes wrote:
Additional update: If on the env.py I substitute "__table_args__ =
{'schema': 'notifications'}" for "__table_args__ = {'schema':
'notifications'}" and rerun alembic twice again (assuming we start on
a clean database), alembic_version is created
On 9/22/15 3:43 PM, Sergi Pons Freixes wrote:
2015-09-22 11:52 GMT-07:00 Sergi Pons Freixes <sachiel2...@gmail.com
<mailto:sachiel2...@gmail.com>>:
2015-09-22 10:41 GMT-07:00 Mike Bayer <mike...@zzzcomputing.com
<mailto:mike...@zzzcomputing.com>>:
On 9/22/15 6:49 PM, Sergi Pons Freixes wrote:
2015-09-22 15:06 GMT-07:00 Mike Bayer <mike...@zzzcomputing.com
<mailto:mike...@zzzcomputing.com>>:
OK, the only possible way this would happen is if "SELECT
current_schema()" were returning the name "notifica
On 9/21/15 8:14 PM, Sergi Pons Freixes wrote:
2015-09-21 16:55 GMT-07:00 Mike Bayer <mike...@zzzcomputing.com
<mailto:mike...@zzzcomputing.com>>:
Can you run the above with logging enabled? That is the [alembic]
logger turned on as in the default alembic.ini.
On 9/21/15 7:32 PM, Sergi Pons Freixes wrote:
2015-09-21 16:13 GMT-07:00 Mike Bayer <mike...@zzzcomputing.com
<mailto:mike...@zzzcomputing.com>>:
Are you sure you don't have any in-application event handlers or
similar manipulating search_path? Can you put this in you
On 9/21/15 10:18 AM, Ofir Herzas wrote:
rename_table operation does not rename sequences if they exist.
This causes a problem that the renamed table is unusable since the
sequence is missing.
In Oracle, a simple rename works well (RENAME old_seq_name TO
new_seq_name;) although it says
On 9/18/15 7:43 PM, Sergi Pons Freixes wrote:
Hi everybody,
I am experiencing the same issue commented
here: https://bitbucket.org/zzzeek/alembic/issues/293/alembic-autogenerate-creates-endless
In my case, I have the model:
---8<--
...
class EmailAttachment(Base):
On 12/11/2015 04:39 PM, Ofir Herzas wrote:
> Hi Mike,
> I've just checked my code and I noticed that I already use existing_type
> (not sure what was wrong with the documentation in that aspect).
>
> Can you elaborate a bit on specifying custom rules as you mentioned?
> I tried issuing a
SQLAlchemy release 1.0.10 is now available.
Release 1.0.10 continues with maintenance fixes as we continue major
development on the 1.1 series. Fixes here include a handful of fairly
obscure ORM issues, as our userbase continues to use the new loader
option system introduced in 0.9 more deeply,
On 12/10/2015 08:39 AM, Ofir Herzas wrote:
> I'm trying to run an alter_column operation from a Boolean type column
> to SmallInteger on Oracle.
>
> According to the documentation: "...Type changes which are against the
> SQLAlchemy “schema” types |Boolean|
>
On 01/02/2016 01:18 PM, Nana Okyere wrote:
> Disclosure: I'm a newbie :-)
>
> Starting with an empty table, I autogenerate and then do upgrade and it
> works fine the first time. When I make a small change to the model(s)
> like adding a new column, then I do autogenerate, alembic generates
the general idea here is to make your own Alembic command runner, create
a Config dynamically and then invoke the alembic commands via
alembic.command.foo() from that.
See http://alembic.readthedocs.org/en/latest/api/commands.html and
SQLAlchemy release 1.0.11 is now available.
Release 1.0.11, only twelve days after 1.0.10's release, is expedited to
correct for one ORM-related regression introduced by a 1.0.10 fix; some
other fairly significant bugfixes involving more recently added
features, all reported subsequent to the
https://bitbucket.org/zzzeek/alembic/issues/351/autogen-with-constraint-names-that-were
is added
On 12/27/2015 07:57 PM, Mike Bayer wrote:
> that is kind of a bug for the time being. You'd need to name those
> constructs explicitly or exclude them using an include_object routine
> (s
On 11/18/2015 06:41 PM, Chris Frey wrote:
> In the alembic documentation, there is an entire page devoted to naming
> constraints:
>
> http://alembic.readthedocs.org/en/latest/naming.html
>
> So I assumed that if constraints had a naming scheme defined, then
> those names would be
On 11/19/2015 04:01 AM, Chris Frey wrote:
> On Wed, Nov 18, 2015 at 11:23:11PM -0500, Mike Bayer wrote:
>> if you change your naming convention, then that would show up as a bunch
>> of brand new constraints in the model and a whole bunch of constraints
>> removed in th
On 06/09/2016 05:11 AM, Søren Løvborg wrote:
On Wed, Jun 8, 2016 at 4:32 PM, Mike Bayer <mike...@zzzcomputing.com
<mailto:mike...@zzzcomputing.com>> wrote:
Branch labels are exactly what solves this?What's wrong with
using a branch label? you put "v1.2.1&q
op.get_bind().name should do it
On 06/03/2016 03:25 AM, Michal Petrucha wrote:
Hi everyone,
I remember seeing a quick expression that extracts the name of the
dialect in use from alembic.op, but I can't find it anywhere now, and
I can't figure it out by myself either. Does anybody know the
op.get_bind().engine.name
On 06/03/2016 10:21 AM, Michal Petrucha wrote:
On Fri, Jun 03, 2016 at 10:05:31AM -0400, Mike Bayer wrote:
op.get_bind().name should do it
Alas, I have already tried that:
if op.get_bind().name == 'postgresql':
AttributeError: 'Connection' object has
the "existing type" comes from what is reflected from the database and
your custom type is not automatically reflectable.
The "existing type" for a PG alter_column is not important here because
Postgresql's "ALTER COLUMN" doesn't require it. It's mostly for MySQL
and SQL Server that
On 06/08/2016 09:21 AM, Søren Løvborg wrote:
Hi,
What's the best practice for "tagging" an Alembic revision, that is to
denote e.g. that 1ffbeb5179a5 is the database revision matching version
1.4.0 of the software?
I can do it in documentation, of course, but would prefer a method
allowing
On 02/06/2016 05:26 PM, Jonathan Beluch wrote:
Thanks for clearing all that functionality up. Will give the traversal a
shot.
On 02/05/2016 01:10 PM, Jonathan Beluch wrote:
> Just realized #4 isn't so simple either as the comparison is
always done
> by name.
if this is
resending because my PGP tools totally got in the way
On 01/22/2016 09:05 AM, Michal Petrucha wrote:
> On Fri, Jan 22, 2016 at 01:44:38PM +0100, Michal Petrucha wrote:
>> Can anyone help me come up with the best way of renaming a Boolean
>> column on both backends? I'm about to try creating a new
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 01/22/2016 07:44 AM, Michal Petrucha wrote:
> Hello people,
>
> I'm having difficluty changing the type of a column from Boolean
> to Integer on SQLite. Boolean generates an integer column with a
> CHECK constraint; changing the type should
test
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy-alembic" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sqlalchemy-alembic+unsubscr...@googlegroups.com.
For more options, visit
SQLAlchemy release 1.0.12 is now available.
Release 1.0.12 is a bug fix release resolving a handful of issues
reported in the past few weeks. Primary development continues on the 1.1
series which is slated for initial releases in the spring.
1.0.12 includes relatively minor fixes,
Alembic 0.8.5 is now available.
Version 0.8.5 includes a short set of bugfixes. See
http://alembic.readthedocs.org/en/latest/changelog.html#change-0.8.5.
Download Alembic 0.8.5 at:
https://pypi.python.org/pypi/alembic
--
You received this message because you are subscribed to the Google
On 04/11/2016 12:34 PM, Zack S wrote:
(X-Post from Stackoverflow: http://stackoverflow.com/q/36511941/703040)
I'm writing some custom code for Alembic to keep my database always
updated in my dev environment for a project. The project involves a
database with the following:
* A |public|
On 04/26/2016 01:22 AM, Amit Saha wrote:
On Tue, Apr 26, 2016 at 12:33 PM, Mike Bayer <mike...@zzzcomputing.com> wrote:
On 04/25/2016 08:30 PM, Amit Saha wrote:
Hi all,
In my scenario, DB migrations (via alembic) will be run as part of the
app deployment and multiple app deplo
Wed, Apr 27, 2016 at 12:37 AM, Mike Bayer <mike...@zzzcomputing.com
> <javascript:;>> wrote:
> >
> >
> > On 04/26/2016 01:22 AM, Amit Saha wrote:
> >>
> >> On Tue, Apr 26, 2016 at 12:33 PM, Mike Bayer <mike...@zzzcomputing.com
> <javascript
On 04/25/2016 08:30 PM, Amit Saha wrote:
Hi all,
In my scenario, DB migrations (via alembic) will be run as part of the
app deployment and multiple app deployments will happen near
simultaneously (multiple EC2 instances talking to the same MySQL DB).
Let's, for simplicity's sake assume two
This depends on how you are sending Alembic its configuration. If you
are running with a plain alembic.ini file, "script_location" should be
present in the file itself, see the example in
http://alembic.readthedocs.io/en/latest/tutorial.html#editing-the-ini-file
Otherwise if your setup is not
Alembic 0.8.6 is now available.
Release 0.8.6 fixes a small handful of bugs including in the area of
batch migrations and Postgresql server default comparison.
It also enhances the behavior of the "alembic revision" command, such
that if the revision fails due to a compile-time or runtime
On 04/18/2016 10:56 AM, bertr...@cryptosense.com wrote:
Hi,
Here's something quite fundamental I don't understand about alembic.
I've initialized my database and created a revision meant to be executed
online. I went like this:
|
alembic init app/alembic
# edit configuration
alembic revision
SQLAlchemy release 1.0.17 is now available.
The 1.0.x series is well into maintenance mode and most fixes and
enhancements are targeted only at the 1.1.x series. This release
includes only one ORM related fix as well as repairs to deprecation
warnings that are more prevalent with the Python
On 09/07/2016 10:18 AM, Chris Withers wrote:
Hi All,
I have a migration which adds a column to a table where the added column
forms part of the primary key.
woe be unto you
:)
As a result, I need to alter the primary key of the table. Autogenerate
doesn't appear to spot this, so
SQLAlchemy release 1.0.15 is now available.
Release 1.0.15 features a small number of bug fixes that have been made
over the past two months since the previous 1.0.x release.
Users should review the changelog for 1.0.15 at
http://www.sqlalchemy.org/changelog/CHANGES_1_0_15; we'd like to
On 09/22/2016 02:51 AM, Tom Walter wrote:
I work in a team of people collaborating on database development and
we'd like to start version controlling and deploy our changes with Alembic.
I was wondering though if there is a way to generate the DDL for the
current state of the whole schema as
On 09/29/2016 07:52 PM, Wesley Weber wrote:
I have an uncommon use case that might or might not be supported (or
even a good idea):
I have a main, independent project with its own tables. I would like to
keep track of migrations of its database. I will also have several
"plugin" projects,
Alembic 0.8.9 is now available.
The release includes seven bug fixes.Changelog is available at:
http://alembic.zzzcomputing.com/en/latest/changelog.html#change-0.8.9
Download alembic 0.8.9 at https://pypi.python.org/pypi/alembic.
--
You received this message because you are subscribed to
SQLAlchemy release 1.1.4 is now available.
Release 1.1.4 includes a variety of bug fixes, some backported to the
1.0 series and others which repair minor regressions in the 1.1 series.
There is also an important fix to the new Postgresql ON CONFLICT
feature, as well as a new feature allowing
SQLAlchemy release 1.0.16 is now available.
Release 1.0.16 includes a series backported bug fixes from SQLAlchemy
versions 1.1.0 to 1.1.4. These changes include a handful of relatively
minor ORM and MS SQL Server fixes.
Changelog for 1.0.16 is at:
SQLAlchemy release 1.1.2 is now available.
Release 1.1.2 includes a small handful of bug fixes, including some
small regressions from the 1.0 series, some ORM loading improvements,
and a fix to the new PostgreSQL ON CONFLICT feature.
Changelog for 1.1.2 is at:
MyISAM does not actually record foreign key definitions. Autogenerate
is not compatible with foreign keys that are declared in the model yet
are not actually present in the database due to MyISAM. To keep these
FK definitions in Python but work around the autogenerate issue, create
an
SQLAlchemy release 1.1.7 is now available.
Release 1.1.7 includes several bugfixes, one of which was introduced in
1.1.6 as a result of performance enhancements for joined eager loading
which presents as a race condition under certain multithreaded
scenarios. Fixes also include an important
SQLAlchemy release 1.1.8 is now available.
Release 1.1.8 is only a few days past 1.1.7, however is being released
early in order to deliver a few fixes requested by downstream projects.
In particular, a regression from the 1.0.x series involving the
sqlalchemy.ext.mutable extension is
SQLAlchemy release 1.0.19 is now available.
This release modifies the just-released fix for Oracle "WITH_UNICODE"
mode based on feedback from cx_Oracle developers, to resolve a
performance regression caused by this change.
Changelog for 1.0.19 is at:
SQLAlchemy release 1.1.13 is now available.
This release modifies the just-released fix for Oracle "WITH_UNICODE"
mode based on feedback from cx_Oracle developers, to resolve a
performance regression caused by this change.
Changelog for 1.1.13 is at:
SQLAlchemy release 1.0.18 is now available.
This release repairs an issue in the test suite that would prevent the
suite from passing on Python version 3.6.2. The release is made at the
same time as that of release 1.1.12 and 1.2.0b2. Additionally, a
backport from release 1.1.7 allowing cx_Oracle
SQLAlchemy release 1.1.12 is now available.
This release repairs an issue in the test suite that would prevent the
suite from passing on Python version 3.6.2. The release is made at the
same time as that of release 1.0.18 and 1.2.0b2. Also included are
fixes related to ORM use of JSON NULL
more straightforward would be a pull request that adds "mysql_after"
keyword to both op.add_column() and op.modify_column().
On Fri, Jul 7, 2017 at 1:33 AM, wrote:
>
>
> On Tuesday, August 27, 2013 at 9:31:29 AM UTC-5, Michael Bayer wrote:
>>
>>
>> On Aug 26, 2013, at 11:49
On Tue, Aug 8, 2017 at 6:14 AM, Sandeep Srinivasa wrote:
> hi guys,
> I'm just taking over a legacy piece of code where tables were hand created
> (SQL).
>
> I'm trying to migrate this over to alembic. I dont have (want to use) any
> python models, so this is alembic by itself.
On Aug 5, 2017 8:40 AM, "Philippe Lavoie"
wrote:
Let's say you're on branch and you have a migration, you test it out, it
works: everything is cool. The version in `public.alembic_version` is your
latest migration.
Before you merge it you have to switch to a different
for one of them. If it sees
unfamiliar identifiers in the table it doesn't know whether or not to
delete it or leave it alone.
Thanks for your reply :)
On Sat, Aug 5, 2017 at 9:02 AM, Mike Bayer <clas...@zzzcomputing.com> wrote:
>
>
> On Aug 5, 2017 8:40 AM, "Philippe Lavoie&q
SQLAlchemy release 1.1.11 is now available.
Release 1.1.11 includes a series of fixes providing
forwards-compatibility with a variety new behaviors in supported
databases. A few other core fixes and one ORM-related fix is also included.
Changelog for 1.1.11 is at:
On 06/07/2017 04:44 PM, Michael wrote:
Hi all, I have a class called MediaChapter(Base), which I've refactored
into MediaBase(Base) and MediaChapter(MediaBase) When I run the
migration, I see:
|
psycopg2.IntegrityError:insert orupdate on table "mediachapter"violates
foreign key constraint
On Sat, Oct 14, 2017 at 11:16 PM, Srikanth Bemineni
wrote:
> Hi,
>
> When I auto generate a migration using alembic, it automatically drops some
> dynamically created tables which are in the DB schema. These tables are
> dynamically created by my application. These
SQLAlchemy release 1.2.0b3 is now available.
Release 1.2.0b3 is possibly the last beta release before 1.2.0 final
is released. The release of 1.2.0b3 was delayed by two major factors.
One was the release of cx_Oracle 6.0, which is a complete rework of
the underlying client library for cx_Oracle
SQLAlchemy release 1.1.14 is now available.
This release includes a variety of fixes for the ORM. Two of the
issues are critical stability issues involving garbage-collection
related bugs that are more likely to be seen within the Pypy
interpreter however are not necessarily limited to this
On Wed, Sep 6, 2017 at 3:12 AM, wrote:
> Hello,
>
> I am a bit puzzled over modeling One-to-One relationships. The example in
> the documentation says to use uselist flag on the relationship declaration.
> That does make sense to ensure scalars on both sides of the
On Sun, Oct 1, 2017 at 7:41 PM, wrote:
> I've used in my generated migration script:
>
> log = logging.getLogger(__name__)
> log.setLevel(logging.INFO)
>
> for now and that seems to work; quick glance at Alembic’s code indicates
> that’s what Alembic uses as well. The
On Mon, Oct 2, 2017 at 9:06 PM, hatch wrote:
> from myapp.mymodel import Base
> target_metadata = Base.metadata
>
> http://alembic.zzzcomputing.com/en/latest/autogenerate.html
>
> What is the preferred way to access myapp? As far as I can tell it's not
> normally available
On Wed, Aug 30, 2017 at 7:18 AM, wrote:
> Given an Alembic migration, would you recommend the following code to rename
> constraints?
>
> from alembic import op
> import sqlalchemy as sa
> from srv.orm.meta import NAMING_CONVENTION # as per Pylons cookiecutter
> template
Unfortunately there's no RENAME CONSTRAINT directive, so dropping and
recreating is how it has to go.
Alembic and SQLAlchemy together do have the ability to return lists of
constraints and produce CREATE instructions for them. Recently I did
some of this related to foreign keys, and the same
hing like an equivalent of the following but for
> Alembic?
>
> https://github.com/plumdog/django_migration_testcase
>
> cheers,
>
> Chris
>
>
> On 01/12/2017 15:06, Mike Bayer wrote:
>>
>> it's kind of a PITA but in Openstack we have fixtures which actually
>&g
1 - 100 of 178 matches
Mail list logo