[Cayenne-dev] Discussing 1.2.3 and 2.0.3 release

Well, I've discovered another one (at least in 1.2, which implies 2.0,
also), but haven't tracked it down enough yet. I don't think it has
anything to do with our binary PKs, either. In a nutshell, I had optimistic
locking turned on everything, including relationships and had:

A ->> B (A to-many-to B)

When I updated attributes in A and B and committed the changes, I'd get an
optimistic locking exception because the SQL generated looked like:

UPDATE A set foo = 'bar'
WHERE primaryKey IS NULL AND ...

For some reason, it is nulling out the PK when figuring out the
differences. (Strangely, it doesn't null out the PK in B -- it was updating
before the A record and the PK was there.) I just haven't had time to track
it down. My solution was to uncheck optimistic locking.

I'm not opposed to a new release, but I know there is something lurking
there, too.

Thanks,

/dev/mrg

Michael, this might be fixed if you're using the outer-join patch. I
seem to recall a similar situation that was cleaned up when I
reorganized the query translator classes. Might be worth a quick
check if you don't mind applying the patch and giving it a whirl.

I'm not opposed to patches. I'm having to maintain my own 1.2, anyway. :-)

Thanks!

/dev/mrg

I'd like to hold off until I can address CAY-763 this weekend. Given
that it could potentially improve the XML stuff and x.y.3 has another
XML code fix, grouping both together in the same release would be
benefial to people using the XML coding.

CAY-722 (less locking of shared cache) is the most important issue
for me now, but it is probably a change that should not go in to any
of the stable branches. I will run it in production for ca a week
before checking in the fix to trunk if everything works well.

- Tore.

So, we had a report from Michael about a potential bug, an issue Tore
is working on that goes on trunk, and CAY-763 that Kevin marked as
resolved a few days ago. Looks like there are no more show stoppers,
so I am going to start a separate vote thread later today.

Andrus

I haven't had time to explore that potential bug yet and wouldn't want to
hold up a bug-fix release on that account.

Thanks,

/dev/mrg

I got the procedure backwards again. We need to build the release
artifacts before we do the vote. I'll need a few more days to do
that. If Kevin or someone else wants to participate in this, please
let me know - we'll schedule some time.

Andrus

I'd be willing to give a hand. I'd have to look at my availability, but
my guess is that sometime Sat. morning - early afternoon (EDT) would
work.

Sounds good. I should have time on Saturday or if not - on Sunday.
I'll know for sure tomorrow. Time permitting, I'll try to look at
CAY-783 and CAY-784 before that.

Andrus

It looks more like Sunday for me. Kevin would you be available on
Sunday morning?

Andrus

Unfortunately, Sunday morning is a no go for me. I have some aggression
to take out on the soccer pitch ;-) I can do Sunday afternoon, however.
Once again, I'm EDT. Are you stateside or euroside right now?

Euroside. Still we can do it if it is not too late in the afternoon.
2-3 pm est?

Andrus

Let's shoot for 3PM my time then. That'll allow me to make sure I'm
back home and what not.

Anyone else care to join?

I have a tennis match scheduled at 1pm and another at 5pm (EDT) on Sunday
and have to refuel in-between, so I doubt I could join for long (and
probably not at 3pm). I'd like to be able to help out, but it feels like we
are herding cats here. :-)

Thanks,

/dev/mrg

Yeah looks like that :-)

Anyways, 3 pm works for me, and gives me the time to test a fix for
the nasty race condition that I just found (CAY-786).

Andrus

Hello.

I could join working hours (CET) next week, but my weekend are full.
Buying/Selling house, getting baby #2 and so on.

- Tore.

What, giving birth is going to take up your whole weekend? :-)

I am around a bit this weekend, but 3pm EST is 5am for me, so I might
need to pass. But if there is anything I can do to help before or
afterward, run any tests, or write up the release notes for the web
site, please let me know. My work is all in Cayenne 3.0 so I don't
have a test environment for 1.2 or 2.0 other than running the junit
tests which probably doesn't really add much to what you guys are
already doing.

So that it isn't forgotten, I've added the 'after release' notes to
the 2.0 release docs, including instructions for updating the DOAP file.

Cheers
Ari



-------------------------->
Aristedes Maniatis
phone +61 2 9660 9700
PGP fingerprint 08 57 20 4B 80 69 59 E2 A9 BF 2D 48 C2 20 0C C8

Hear you. In a very similar situation myself (plus I work from home
so that's going on 24x7 :-))

Anyways, once we post the release artifacts, we still need to do the
review and testing, giving everybody who is willing to help more time
flexibility.

Thanks
Andrus