Quick EOModel Column Locking ?

2016-03-19 Thread Jeff Schmitz 
I’m starting to get some optimistic column locking failures during background 
db processing soI’m trying to grasp conditions under which I don’t need to lock 
a column (i.e. put the little lock symbol in EOModeler) 

If I have a column in a table that I know is not updated (i.e. changed) by any 
client except form my personal administrative page, can I get away without 
locking that column?On unlocked columns is there any where clause checks 
such as shown below before that column is updated?  If not, this should stop 
the locking errors, right?  Any other dangers with this?

update Person set FirstName = 'Robert' where PersonID = 123 and FirstName = 
'Bob' and LastName = 'Roberts'
Finally, to make this change Is it as simple as unchecking the column and 
redeploying my EOModel file?

Thanks!
Jeff ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Quick EOModel Column Locking ?

2016-03-19 Thread Chuck Hill 
Hi Jeff,

Yes, if a column is not marked as locking, then it won’t appear in the WHERE 
clause.

The danger is that you might save changes that are inconsistent with what the 
database has stored in the columns that you are not locking on.  As a contrived 
example, consider the update below changing Bob to Robert.  If you don’t lock 
on first and last name, some other process might have updated both names to 
John Edwards.  Your update will now change the name to Robert Edwards.  You 
need to look at your data and see where that might matter and where it does not.

Chuck


From: 
mailto:webobjects-dev-bounces+chill=gevityinc@lists.apple.com>>
 on behalf of Jeff Schmitz 
mailto:jeffschm...@icloud.com>>
Date: Thursday, March 17, 2016 at 5:20 PM
To: WebObjects Development 
mailto:webobjects-dev@lists.apple.com>>
Subject: Quick EOModel Column Locking ?

I’m starting to get some optimistic column locking failures during background 
db processing soI’m trying to grasp conditions under which I don’t need to lock 
a column (i.e. put the little lock symbol in EOModeler)

If I have a column in a table that I know is not updated (i.e. changed) by any 
client except form my personal administrative page, can I get away without 
locking that column?On unlocked columns is there any where clause checks 
such as shown below before that column is updated?  If not, this should stop 
the locking errors, right?  Any other dangers with this?


update Person set FirstName = 'Robert' where PersonID = 123 and FirstName = 
'Bob' and LastName = 'Roberts'

Finally, to make this change Is it as simple as unchecking the column and 
redeploying my EOModel file?

Thanks!
Jeff
 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Quick EOModel Column Locking ?

2016-03-19 Thread Philippe Rabier 
Jeff, if you remove the lock, you have a risk to get a write-write conflict, 
aka a write replaced by another. It’s maybe not a big deal. I don’t know.

Another solution, if you are sure your background db process is the only one to 
modify an attribute, is to use raw sql to update the column you want to modify.

Philippe

> On 18 mars 2016, at 17:42, Jeff Schmitz  wrote:
> 
> Thanks Chuck,
>Yep, I understand the issue with inconsistent data, but most of my 
> attributes are not semantically dependent on other attributes in that way  If 
> that’s all the locks are guarding against I’ve got some lock trimming to do.
> 
>> On Mar 18, 2016, at 11:11 AM, Chuck Hill > > wrote:
>> 
>> Hi Jeff,
>> 
>> Yes, if a column is not marked as locking, then it won’t appear in the WHERE 
>> clause.
>> 
>> The danger is that you might save changes that are inconsistent with what 
>> the database has stored in the columns that you are not locking on.  As a 
>> contrived example, consider the update below changing Bob to Robert.  If you 
>> don’t lock on first and last name, some other process might have updated 
>> both names to John Edwards.  Your update will now change the name to Robert 
>> Edwards.  You need to look at your data and see where that might matter and 
>> where it does not.
>> 
>> Chuck
>> 
>> 
>> From: > > on 
>> behalf of Jeff Schmitz > >
>> Date: Thursday, March 17, 2016 at 5:20 PM
>> To: WebObjects Development > >
>> Subject: Quick EOModel Column Locking ?
>> 
>> I’m starting to get some optimistic column locking failures during 
>> background db processing soI’m trying to grasp conditions under which I 
>> don’t need to lock a column (i.e. put the little lock symbol in EOModeler) 
>> 
>> If I have a column in a table that I know is not updated (i.e. changed) by 
>> any client except form my personal administrative page, can I get away 
>> without locking that column?On unlocked columns is there any where 
>> clause checks such as shown below before that column is updated?  If not, 
>> this should stop the locking errors, right?  Any other dangers with this?
>> 
>> update Person set FirstName = 'Robert' where PersonID = 123 and FirstName = 
>> 'Bob' and LastName = 'Roberts'
>> Finally, to make this change Is it as simple as unchecking the column and 
>> redeploying my EOModel file?
>> 
>> Thanks!
>> Jeff
> 
> ___
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/prabier%40icloud.com
> 
> This email sent to prab...@icloud.com

 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: frameworksBaseURL borked after Wonder update

2016-03-19 Thread Hugi Thordarson 
Hi Markus,

my build files have a section that looks exactly like the one you posted, so 
that’s not a solution.

Note: I’m not making URLs for WebServerResources, the Resources in question are 
from “Resources”.

- hugi



> On 16. mar. 2016, at 10:44, Dr. Markus Stoll, junidas GmbH 
>  wrote:
> 
> Hi Hugi,
> 
> now I understand whats happening, obviously there are 2 different ant 
> build.xml templates in the wild, one creating embedded frameworks webserver 
> resources in
> 
> /WebObjects/${build.app.name}.woa/Frameworks
> 
> which is the old default scheme (and wocommunity pages still are referring to 
> this one) and another one creating
> 
> /WebObjects/${build.app.name}.woa/Contents/Frameworks
> 
> 
> 
> ERXDeploymentBundle does not know about the latter and cannot detect this 
> automatically.
> 
> For now changing your ant script to the old scheme would help, changing your 
> section for creating the WebServerResources part using a copy statement like 
> this
> 
>
>
>
>
>
>
>
>
> 
> I will propose a solution for ERXDeploymentBundle
> 
> 
> Regards, Markus
> 
> 
>> Am 15.03.2016 um 23:15 schrieb Hugi Thordarson :
>> 
>> Hi Markus,
>> 
>> I’m building with Ant.
>> 
>> ERXDeployedBundle is apparently hardcoding the URL to be App.woa/Frameworks, 
>> so that explains why my URLs are now broken:
>> 
>> https://github.com/markusstoll/wonder/blob/4e5e98a4a7c6f7251054820f636beeb629828f1d/Frameworks/Core/ERExtensions/Sources/er/extensions/appserver/ERXDeployedBundle.java#L84-L86
>> 
>> So… If this is what it should be, then why have my apps always placed 
>> embedded frameworks at /App.woa/Contents/Frameworks and how do I change my 
>> builds?
>> 
>> Cheers,
>> - hugi
>> 
>> 
>> 
>>> On 15. mar. 2016, at 21:55, Markus Stoll, junidas GmbH 
>>>  wrote:
>>> 
>>> Hi,
>>> 
>>> see my pull request #727
>>> 
>>> I had the impression that difference is between maven builds and ant builds 
>>> - I would be pleased if someone could clarify, what introduced this change
>>> 
>>> Markus
>>> 
>>> 
 Am 15.03.2016 um 16:53 schrieb Hugi Thordarson :
 
 Hi all.
 I just updated to the most recent version of Wonder (unfortunately I have 
 no idea how old the version I was replacing was).
 Now URLs to resources in embedded frameworks are wrong, i.e. they no 
 longer contain the “Contents” part of the woa-bundle, so they look like 
 this:
 
 …/Hugi.woa/Frameworks/USWebObjects.framework/Resources/main.css
 
 instead of this (where the resources are actually found):
 
 …/Hugi.woa/Contents/Frameworks/USWebObjects.framework/Resources/main.css
 
 
 Setting frameworksBaseURL in build.xml does not seem to change anything. 
 Any ideas?
 
 Cheers,
 - hugi
 ___
 Do not post admin requests to the list. They will be ignored.
 Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
 Help/Unsubscribe/Update your Subscription:
 https://lists.apple.com/mailman/options/webobjects-dev/markus.stoll%40junidas.de
 
 This email sent to markus.st...@junidas.de
>>> 
>> 
> 


 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com