Thanks Sharoon for your reply.
I am using this method now. and stop() the transaction to check how it
works.
you are right and now it is part of my work.
To appreciate your long reply i am asking new question as i am still a
beginner here.
when i worked with a combination of enterprise patterns from Microsoft
patterns and practice few years ago
in combination with another wrapper to act like a facade pattern, We
had 2 different method to use the ORM system.
Simply creating new objects like Tryton 1.6 was available and we could
simply use obj.save()
BUT, we also could take advantage of a new Transaction() class, this
Class helped us to wrote some important peaces of code and then call
them as a transaction.
another methods like rolling back and few other features were
available within the library.
those days we used the simple save() for creating records like party
in Tryton.
But for some important one which contains for examle adding too many
save() which has been related together we used Transaction.


I am not specialist in developing ORM itself. But i can imagine using
a transaction every time for even simple interaction with database is
not beautiful enough.
But i can't allow myself to complain about it when i don't know how
how the whole Tryton framework and Transaction work , I think Cedric
knows better. So i only can tell you that it is disappointing for me
to call functions
one by one.


I would like to add something for the meaning of Disadvantage to avoid
any misunderstanding.

Few years ago i was a big fan of GTA3 it was really much better than
other competitors like NeedforSpeed etc..
in addition i had a little experience of dealing with DirectX from
Microsoft as wel as exploring OpenGL, and it was my fan to be a game
developer those days :)
Therefore in my opinion, this game really really didn't have any
disadvantages !!! i checked all part of the game and played with it.
Then i curiously went to see what would be on the PC Magazine,
I saw an review for this game with the highest rate i had ever seen in
the game review in PC Magazine.
But in terms of disadvantage they wrote this :

"Only can be run on fast and expensive Graphic adapters!"

Yes it was true, There were nothing else to complain about this game
but this one WAS a disadvantage.

Lets look around, Everybody hates Microsoft, They have to maintain the
compatibility to keep their customers to continue working on it. You
can see that almost any device around the world has a drive to work on
windows and everybody want Microsoft to work fast and understand the
device in plug and play mode.
Microsoft instead compatibility but this advantage has an important
disadvantages. Complexity ! Only few developers in Apple work on MaxOS
and they are able to deliver an OS which is more beautiful and even in
some cases faster than windows ! But in Microsoft they have to spend
too much money to have these kind of features !
So i think it is a RULE,
Tryton is not a huge on demand ERP system. (NOT YET! I HOPE I WILL
BE) , So you don't have to hear lots of complains about compatibility
problem. Yes You break the rule and 1.8 is not compatible with 1.6.
Everyone have to rewrite their code. But neither me nor anyone else
didn't post anything about it, Why ? because this Tryton Team is mouse
and Bigger companies like OpenERP are Elephant.
We have another Rule in Management:

Elephants can't dance !

So OPENERP can't dance and resolve these kind of problems in such a
fast time. But Here we can. But let me remind you this Rule that this
new feature has disadvantages on behind. you believe my
word when you get experienced it in the future of Tryton, When it
becomes bigger.

Of course i am new and maybe even i don't understand the concept
behind the Transaction Manager. But just want to share my idea to many
people like me who are standing at the first point. as this is the
best way to learn.
I learned from the posts a lot.

Regards,
Mohammad

On Dec 1, 5:07 pm, Paul J Stevens <[email protected]> wrote:
> On 12/01/2010 09:40 AM, "C dric Krier" <[email protected]>" wrote:
>
> > On 01/12/10 00:10 -0800, Mohammad wrote:
> >> Maybe it is time for me to migrate to this Poteus , A client library
> >> to work with ORM.
>
> > Be careful that with Proteus you don't have access to the management of the 
> > DB
> > transaction. So after each call, the transaction is commited as it will be
> > from the client.
>
> Wasn't adding transaction management to proteus on your todo or r&d list?
>
> --
>   ________________________________________________________________
>   Paul Stevens                                      paul at nfg.nl
>   NET FACILITIES GROUP                     GPG/PGP: 1024D/11F8CD31
>   The Netherlands________________________________http://www.nfg.nl

-- 
[email protected] mailing list

Reply via email to