Hi Gautam,
Bring in OFBiz updates into a separate exploratory branch. Keep maintaining and evolving your
trunk. Over time, evolve your trunk to align more with OFBiz. With branches, you are not forced to
align disparate branches of development immediately.
There will be some areas where your trunk cannot reconcile with OFBiz updates, nor would you want
reconciliation there. Again, with SVN techniques, you can keep those areas insulated during your
updates.
For the particular example with PartyGroup.federalTaxId, it could simply be a further
normalization of the database, a refinement. You should keep in step with the normalization, if
you can afford the time to do so. Most, if not all, updates to OFBiz are thought-out and correct.
But please still check before merging updates into your trunk.
Jonathon
Jacques Le Roux wrote:
Hi Gautam,
This quick answer is only my opinion and may not reflect the community.
OFBiz is a real community driven open source project. There are no teams
intended to support users. This project is moving forward. If you want to be
sure not to find yourself in troubles such as those you described you should
stick to a revision number or even better to a release. The advantage with a
release is that bug fixes will be applied on it by the community; you don't
have to care by yourself on the contrary of a revision number. If you want to
follow progress then you will have to find your own way I guess...
HTH
Jacques
----- Message d'origine -----
De : Gautam Deb
À : dev@ofbiz.apache.org
Envoyé : lundi 30 avril 2007 15:35
Objet : Re: Updating entities after OFBiz update
To give some context to what exactly I mean to say -
1. I am aware of the fact the any addition made to the entities is
automatically taken care by OFBiz. What I referred was any alteration to the
entities like change in the size of the column, change in the data type of a
column, change in the primary key of an entity or change in a relationship
between entities etc.
2. Also what to do in scenarios when some entity field is deprecated and we
are still using it. For example, some time back, the 'federalTaxId' field part
of PartyGroup entity. We were using that entity and our business logic was
dependent on that. In a later release this field was deprecated and moved to
some other entity. What to do in such scenarios?
Thanks & Regards,
Gautam Deb
G.Venkata Phanindra wrote:
Hi Gautam Deb,
Once we Update the OFBiz n start it, automatically new entities are added and from my last two years of experience i never saw the changes in the existing entities relations that will effect the previous revision. hopefully new ones are added and i see enough care is taken by the community so as not to disturb the existing relations.
Hopefully i answered your point as i understood your question.
Regards
Phani
On 4/30/07, Gautam Deb < [EMAIL PROTECTED]> wrote:
What is the best way to update the entities after an OFBiz update?
CURRENT SCENARIO - We are using OFBiz as the framework for our
application. We mainly use the the OFBiz apps Order Manager and Party Manager.
Apart from this we have some custom applications which basically uses the
Entity and Service engine. The OFBiz update process for us is not so frequent.
We update the OFBiz every 4 - 6 months. The problem is that the OFBiz changes a
lot in this duration. For the changes in entities (to be precise any alteration
in the entity) we write manual SQLs and shoot them against the database.
Thanks & Regards,
Gautam Deb
--
G.Venkata Phanindra
Mob:: 9849852989
------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.467 / Virus Database: 269.6.5/792 - Release Date: 5/6/2007 9:01 PM
