on SQLite.
We also can drop SQLite support and in this case:
- We just factor out all that related to SQLite from migrations one time
and set this bug as Won't fix.
Let's discuss that.
--
With kind regards, Andrew Pashkin.
cell phone - +7 (985) 898 57 59
Skype - waves_in_fluids
e-mail - apash
/On 26.01.2015 18:05, Ruslan Kamaldinov wrote:/
/I think it's still important to perform migration specific checks. We
want to make sure that DB is in expected state after each specific
migration./
Why?
On 26.01.2015 18:05, Ruslan Kamaldinov wrote:
On Mon, Jan 26, 2015 at 3:03 PM, Andrew
solution is to drop all current migrations and
introduce new one with correct names.
you definitely shouldn’t need to do that.
Why?
On 30.01.2015 22:00, Mike Bayer wrote:
Andrew Pashkin apash...@mirantis.com wrote:
Working on this issue I encountered another problem.
Most indices
On 26.01.2015 18:34, Ruslan Kamaldinov wrote:
On Mon, Jan 26, 2015 at 6:12 PM, Andrew Pashkin apash...@mirantis.com wrote:
On 26.01.2015 18:05, Ruslan Kamaldinov wrote:
I think it's still important to perform migration specific checks. We want
to make sure that DB is in expected state after
database-specific features (stored procedures
etc).
There are good chances that these cases will never happen in reality, as
I understand, so I tend to agree.
--
With kind regards, Andrew Pashkin.
cell phone - +7 (985) 898 57 59
Skype - waves_in_fluids
e-mail - apash...@mirantis.com
/017d25f49e60e18365a50756f524e15f8d4fa78a/murano/db/services/environments.py#L62
--
With kind regards, Andrew Pashkin.
cell phone - +7 (985) 898 57 59
Skype - waves_in_fluids
e-mail - apash...@mirantis.com
__
OpenStack Development
for some DBs.
3) Do not test such issues at all.
Do anyone has some thoughts on this?
--
With kind regards, Andrew Pashkin.
cell phone - +7 (985) 898 57 59
Skype - waves_in_fluids
e-mail - apash...@mirantis.com
__
OpenStack
/catalog/api.py#L226-226
On 02.03.2015 19:05, Serg Melikyan wrote:
Hi Andrew,
I think we should isolate DB access layer and test this layer
extensively on MySQL PostgreSQL.
On Mon, Mar 2, 2015 at 6:57 PM, Andrew Pashkin apash...@mirantis.com
mailto:apash...@mirantis.com wrote
should not introduce it.
On 02.03.2015 19:05, Serg Melikyan wrote:
Hi Andrew,
I think we should isolate DB access layer and test this layer
extensively on MySQL PostgreSQL.
On Mon, Mar 2, 2015 at 6:57 PM, Andrew Pashkin apash...@mirantis.com
mailto:apash...@mirantis.com wrote
to use.
[1]
http://alembic.readthedocs.org/en/latest/naming.html#tutorial-constraint-names
[2] https://review.openstack.org/150818
--
With kind regards, Andrew Pashkin.
cell phone - +7 (985) 898 57 59
Skype - waves_in_fluids
e-mail - apash...@mirantis.com
10 matches
Mail list logo
