Skip to Main Content

SQLcl

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

SQLcl lb changeset labels and context not working properly?

ianm42May 4 2022 — edited May 6 2022

Using SQLcl 21.4, it appears that the 'context' argument for Liquibase Changesets is being ignored. Changesets with a 'context' specified are applied no matter what context string is supplied in the update or updatesql command, or if no context string is supplied.
Using 'labels' is a little better. If label A is specified in the command, Changesets with labels A are applied and Changesets with labels B are not applied. But if no label is supplied is specified in the command, all the Changesets are applied, A, B and no label.
Is this the expected functionality?

Comments

2796195

Hello,

I have exactly the same problem on my project (EF 5 / EDMX / ODAC 11 / ASP.NET MVC 5 / IIS)

Do you have the same configuration ?


We use 2 different databases. Sometime the problem happens on the first, sometime on the second.

Because we use always first database before second one, when queries for the second database are malformed, that means queries on the first one are wellformed. So the problem seems attached to EDMX schema.

Because LINQ query plan is cached by EF5, when the problem happens, it generates a lot of exceptions until the application pool will be recycled

Greg Bachraty

Hi!

More or less the same setup except no MVC and using ODAC 12cR2. The app uses a single database though other apps on the same IIS (all in different dedicated pools) use others. Even though this test server has ODAC11 installed - some use this, some use instant 12c, some managed 12c - I've also verified that the affected apps always get the correct dll version loaded into their address space.

My dev setup has only one ODAC version (always the latest) and it still bugs out although less frequently. I've tried full installation, instant client, managed client, eventually all produce the problem.

I'm not sure if this is an edmx problem since some of my affected apps haven't changed for more than a year and were working fine back then.

1 - 2

Post Details

Added on May 4 2022
1 comment
567 views