On Dec 26, 12:08 pm, "ak" <[EMAIL PROTECTED]> wrote:
You can search through this mailing list, I remember one guy about a
few months ago that compared django development to his previous php
expirience and found that django is now very well for him.
Unfortunatelly I have no link and I don't
Victor Ng wrote:
> On 11/30/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> > Here you mean SELECT FOR UPDATE, right?
>
> No, I mean SELECT.
OK. Then another part of my answer is applied.
> The use case is two users are viewing the same record, and they both
> go to update the same
Victor Ng wrote:
> If user A and user B are editting the same records and you enter a
> race where they do this:
>
> A) retrieve record
Here you mean SELECT FOR UPDATE, right?
> B) retrieve record
Same here, right?
> A) delete record
> B) update record
As SELECT FOR UPDATE starts a
Victor Ng wrote:
> I find this interesting too since the use of numeric instead of a
> float is the right decision most of the time.
>
> If you're dealing with money at all - you absolutely cannot use float,
> you *must* use fixed decimal types or you risk getting into all kinds
> of really
I appologize for rather provocative subject line. I just want to tell
all why I could not use Django and had to use TurboGears
instead, even though I like Django more. I wrote this memo
for internal use, and then desided to post it inhere.
I have been involved in an initial development of
5 matches
Mail list logo