| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
The method for skipping a test in unittest is skipTest(). testtools also
provides skip(), but that is deprecated. This eliminates the deprecation
warnings by switching to the recommended skipTest().
Change-Id: I45da95958e6f65475beab0d7a3c6de6604fa82d7
|
|\ \
| |/
|/| |
|
| |
| |
| |
| | |
Change-Id: I15095b7a75d240197dc6135ddae69f05e91897c7
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
Change-Id: Idace3cbe1ac3c454443d1c786054dc8ff0b0e8b5
Closes-Bug: #1714842
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| | |
Adjust a test that attempts to verify that a CHECK constraint
has been dropped to use raw SQL, as the Boolean datatype
in SQLAlchemy 1.1 is coercing the target value of "10" to a "1"
in any case. Starting with SQLAlchemy 1.2, the Python-side
Boolean datatype will also raise an error.
Change-Id: I99ffce63f9646323d9e2e3079e52b4829d996ea6
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This method is useless in class BackendImpl.
So it is deprecated for removal.
Change-Id: I3c73acc6b02da731a73880146661b63e75657982
Closes-Bug:#1714778
|
|\ \ \ |
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The change b3869d04cff7071c1226758eb8b58fde9eba5b8d was fixing #1615938
only for some cases, where the unicity of the row was done by one
column.
This change fixes it for other cases.
Change-Id: I4acb382c770b168f29fa35f02707fb22d402b13b
Closes-bug: #1615938
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
For more information about this automatic import see:
https://docs.openstack.org/i18n/latest/reviewing-translation-import.html
Change-Id: I49b20ce3f02d1f3ff34212beb91ccdace086a1c7
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Adds two new functions:
- get_foreign_key_constraint_name() - common function
used in subprojects which retrieves the name of a
foreign key constraint given table name / column name
- suspend_fk_constraints_for_col_alter() - given table name and column
name, locates matching foreign key constraints, drops them,
yields context, then recreates them as they were.
By default only runs for NDB thus avoiding expensive
constraint regeneration on other backends.
Co-authored-by: Mike Bayer <mike_mp@zzzcomputing.com>
Co-authored-by: Paul Bourke <paul.bourke@oracle.com>
Change-Id: I76c0d82fddf38add0ca05be270264b6e2d043f7f
|
|/ / /
| | |
| | |
| | | |
Change-Id: Iad5cb53a0ff45e86b1dafa863fab904f34516a75
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Stop throwing the deprecated DbMigrationError exception,
Use the new DBMigrationError exception instead,
so that the consumers can catch the new exception.
DbMigrationError will not be removed until no consumers
still use it.
Change-Id: Iab0566cf9f4552e91fa417e64472fa106e8bc86d
|
| |/ /
|/| |
| | |
| | | |
Change-Id: I92f8c0cdffb512d154d0c1371a48c25dd2a3d44c
|
|\ \ \
| |_|/
|/| | |
|
| |/
| |
| |
| |
| |
| |
| | |
This patch is proposed according to the Direction 10 of doc
migration(https://etherpad.openstack.org/p/doc-migration-tracking).
Change-Id: I6904da7a5f2bd12cf44d047e4b865389e44fb56b
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| | |
Remove AutoString* in ndb.py including
AutoStringTinyText,AutoStringText,AutoStringSize.
Change-Id: I707d69facb8f4542550243c1b5eff051264f3204
Closes-Bug:#1714913
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| | |
This method is useless in class Backend.
So this method is deprecated for removal.
Change-Id: I4f2aa180e5506172776ffc6f5e2a0111dacc5594
Closes-Bug:#1714776
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
This class in new edition is useless.
So class TransactionResource is
deprecated for removal.
Change-Id: Ie4155736732a04238f8458aec9ae0d9a0f709ad2
Closes-Bug:#1714765
|
|/
|
|
|
|
|
|
|
| |
This class in new edtion is useless.
So class InsertFromSelect is
deprecated for removal.
Change-Id: I200486a5a88e78b5223b9364fbea5901048d5cb9
Closes-Bug:#1714768
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
1.As mentioned in [1], we should avoid using six.iteritems to achieve iterators.
We can use dict.items instead, as it will return iterators in PY3 as well.
And dict.items/keys will more readable.
2.In py2, the performance about list should be negligible, see the link [2].
[1] https://wiki.openstack.org/wiki/Python3
[2] http://lists.openstack.org/pipermail/openstack-dev/2015-June/066391.html
Change-Id: If76115f706e9e100a1780471af0f9c5d92d3bc9f
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The "idle_timeout" name and documentation are misleading to users.
Rename the option to connection_recycle_time to more closely
match that of the underlying SQLAlchemy argument name
"pool_recycle", which refers to a time period for which
a connection present in the pool for longer than that number
of seconds will be closed and replaced with a new one *upon checkout*,
to prevent usage of stale connections that may have been closed by
server-side reapers.
Change-Id: I5e39d5ac81eaa8d85b1dfb18862fe27695ab8b96
|
| | |
| | |
| | |
| | | |
Change-Id: I91e770e8ca54bdf8d8da40d4815ef860f12121be
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
The ndb change that makes use of String.adapt() to produce a new
object breaks on SQLAlchemy < 1.1 because adapt() there does
not allow for kwargs to override those already
present in the type.
Change-Id: I8cc79dc9bebcb3cb3accf76559bc969c2dae7ed9
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
This simplifies the ndb "AutoStringXYZ" series
of classes into a single oslo_db.sqlalchemy.types.String
type which features all necessary behaviors via
two new flags, mysql_ndb_length and mysql_ndb_type.
Change-Id: I7f9c830073bf9a30abce0aa4bb55b5c9cf661afe
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
SQLAlchemy has 2 options of implementing error event listener. It can
either raise exception directly or it can return exception into chain.
With the first option all other handlers are ignored (ref:
http://docs.sqlalchemy.org/en/latest/core/events.html?highlight=context#sqlalchemy.events.ConnectionEvents.handle_error)
OSProfiler is interested to subscribe to SQLAlchemy error events.
However with the current approach only Oslo.DB gets the events.
Change-Id: Ia6bccd5af5f2e38f4333f1cc435f6bb9c12bc09f
Related-Bug: 1706299
|
| |
| |
| |
| | |
Change-Id: Id334c7c2a25b81cedcbcf30863d180f78b0c9512
|
| |
| |
| |
| | |
Change-Id: I7f3f9700f02f4d38b18f6d75f2fd33299451e5cb
|
|/
|
|
|
|
|
|
|
| |
/home/sam/Work/ironic/.tox/py27/local/lib/python2.7/site-packages/oslo_db/tests/sqlalchemy/__init__.py:20:
DeprecationWarning: Function
'oslo_db.sqlalchemy.test_base.optimize_db_test_loader()' has moved to
'oslo_db.sqlalchemy.test_fixtures.optimize_package_test_loader()'
Change-Id: I7fb4e776cedb8adcf97c9a43210049c60f796873
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The scenario where an existing database connection that's
present in the pool is found to be not connected to the
database should normally not be occurring; the idle_timeout
setting (aka pool_recycle) should be less than the effective "idle timeout"
set up on the server and/or HAProxy such that a stale
connection in the pool should already have been recycled.
As a system with a mis-configured idle_timeout can experience
latency due to this error hook, it should be reported that
this is an avoidable situation which is occurring. Right
now there's no easy way to see if a performance test is
spending lots of time hitting this condition or not.
Change-Id: I3e9613cbb982c727762247201c5c4972e21da725
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The connection.info dictionary comes from the underlying
pooled connection, which in a disconnection situation
is not there; trying to access it makes it try to reconnect.
Inside of rollback(), SQLAlchemy doesn't allow us to
reconnect yet because we haven't finished removing the
transctional state that corresponds to the now-discarded
connection. Therefore we have to check connection.invalidated
inside of our rollback handlers before trying to add/remove tokens
from connection.info.
Change-Id: Icd10ada68d6d53410ac88eca3577f04c5e30087e
Resolves-bug: #1704474
|
|/
|
|
|
|
|
| |
* update setup.cfg with right document links
* update HACKING.rst with latest link for hacking
Change-Id: I8eb294c1d734f9c76951e4b4b9ebb0f69183f8f3
|
|\ |
|
| |
| |
| |
| | |
Change-Id: I0f6b5e516813ffd6b90b7283eb893b0d5c3accd0
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Maybe we need to know the original exception when exception occurs on
method 'session.rollback()'.
Change-Id: Iccda37a3279d6f24de69cfccef3e29787f1ac694
Closes-Bug: #1684329
|
| |
| |
| |
| | |
Change-Id: I0b64c644f40a2da3242274194d1a5d2858813c25
|