On Mon, Feb 02, 2009 at 12:38:45PM -0500, Stef Telford wrote:
> Oleg Broytmann wrote:
> > On Sun, Feb 01, 2009 at 06:25:07PM -0500, Stef Telford wrote:
> > No offence taken. :)
>
> good show. I always get worried about people taking offense over
> e-mail. I find that tone is very hard to convey.
I know. I did it many time in this mailing list - inadvertently offended
people. Different levels of English knowledge, different vocabularies,
different understanding...
> > Still I don't understand. What do you mean by saying "there is no
> > contention"? If there are threads and there are shared variables -
> > the variables must be protected, right? Have I missed something?
> > There are global counters, e.g. in Alias - how would they fare if
> > different threads would want to increase them?
>
> Well, at the start of every request, a connection is created to the
> database. Now, -any- rdbms worth it's salt basically creates an
> isolation level so that I can see -my- changes but no one else's
> changes
Aha, I see. We are talking about different concepts. You are talking
about database isolation. I am talking about python shared variables. Those
locks in the code protect python variables, not database! Think about that
very pool, connection._pool - nobody (i.e., no other thread) should read it
even less should write to it until SQLObject finishes manipulating it. The
same is true for alias lock.
> I don't mind tidying up and putting in
> memcache support and master/slave style connections for a web version,
> but I obviously don't want to play 'catch up' with every new release
> that you fellows do.. hrm.
But what was you plan from the beginning? If you were going to have
a forked version of SQLObject - wouldn't fork and catching up the only
option? You can add some code to the very SQLObject, but if you want to
remove some generic code - what is the way?
Oleg.
--
Oleg Broytmann http://phd.pp.ru/ p...@phd.pp.ru
Programmers don't die, they just GOSUB without RETURN.
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
sqlobject-discuss mailing list
sqlobject-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
