Re: Framework EOModels
Re: Framework EOModels
- Subject: Re: Framework EOModels
- From: Chuck Hill <email@hidden>
- Date: Wed, 22 Apr 2015 19:06:44 +0000
- Thread-topic: Framework EOModels
|
Hi Gino,
On 2015-04-22, 10:56 AM, "Gino Pacitti" wrote:
Well if the Framework EOModel is tied to a single DB and set of tables then all the Apps would be using the same data source. Obviously the Apps would have different stacks and freshness would be an issue… but I was more concerned with two records for
the same DB and table being created and saved.
For example a payment system where more than 1 app might use the Framework.
App1 needs to store a transaction ID in a TransactionObject and App2 needs to store a transactionID in a Transaction Object.
That sounds dangerously like transactionID has a user visible meaning. It is a terrible idea to use the PK for that. It is tempting, I admit, but a terrible idea none-the-less. If that is what you are doing, I advise you to reconsider it. If not, just
ignore me. :-)
These objects which have TempGlobalIDs have not been saved as yet but the moment one is saved the EO_PK_Table is updated with a PK for the TransactionObject. But then if the other TransactionObject is attempted to be saved what would happen… would there
be a conflict or as you say are they completely independent and the EOF would handle it and save the other TransactionObject with a non conflicting PK?
When a TempGlobalIDs is made permanent, the permanent value is unique regardless of how many apps are doing this. You have nothing to fear.
Chuck
Assuming you have a specific db for each app of course. If not, the objects are still all independent, but you’ll have to deal with data freshness/communication between the 2 apps as they would access the same storage.
Xavier
On 22 avr. 2015, at 19:42, Gino Pacitti < email@hidden> wrote: Ah Ok.. so even if 10 apps use the same Framework every EOObject is completely safe and no conflicts for PKs…
Great...
Hi Gino,
Everything is completely independent.
No conflict.
That’s actually why you create frameworks;)
Xavier
On 22 avr. 2015, at 19:17, Gino Pacitti < email@hidden> wrote: I was planning a Framework which has an EOModel that two different apps will use. Is there a potential of conflicts when each app tries to create a record and save to db?
Specifically if app1 creates an EOEnterprise Object and modifies it and does not save and at the same time app2 creates an EOEnterprise Object and does save… Does the Framework follow the creation of TempGlobalIDs and does not allow conflicts to occur
when that Framework is being used between apps?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Help/Unsubscribe/Update your Subscription:
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Help/Unsubscribe/Update your Subscription:
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Help/Unsubscribe/Update your Subscription:
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Help/Unsubscribe/Update your Subscription:
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden