Okay, reading the new transaction docs a little closer it looks like
you've implemented method (2) in my message above. Seems to me like
this is the necessary method, the only sane thing to do in web context.
However, since the transactions apply only in short-lived context of
when user is savi
Jacob -- I'm a mostly non-web programmer (with experience in non-web
n-tier apps) trying to figure out exactly what sort of transaction
support this is. Can you clarify for me? Here are the two types of
transactions I'm thinking people might want:
(1) Transaction is begun when a client makes a
"Think distributed: two requests updating the same data concurrently.
Last write wins. Data might not be what you expect, as you can't make
sure that you have the version you directly read before updating. This
is the simple scenario. Often this doesn't matter, as "last write wins"
is quite accept
ZebZiggle --
Sorry, if you're not talking about any sort of auto-refresh at all, and
are just talking about fact that in Django the second user's object
will automatically overwrite the object that the first user just saved
in the db, without any warning or error message, then I agree this is a
p
"That's good to know, but as you have stated previously, transactions
alone won't solve this problem. There still needs to be some concept of
versioning on top of the transactions, which isn't trivial
(arguably/perhaps even harder to do right than supporting transaction
wrappers).
Perhaps we need
Good question.
I would not expect that you'd be able to just "change" the child object
to be a different child object, though. It would make more sense to
have a 'delete' method to remove a child from list of child objects and
then to add a new child object separately. I don't see any delete
me
Glenn -- I think your one to many answer is here:
http://www.djangoproject.com/documentation/models/many_to_one/
-- Herb
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group,
I think the 'core=true' option is used when you're defining a lookup
field that is to be edited on another object's page.
In the model api docs it says that 'blank = True' is the option you
want to use to make entry optional, otherwise field is required to be
entered, i.e., non-blank:
http://www.
Have you taken a look at the Many-to-many relationships example? Looks
like you're trying to manually create the links between tables, whereas
you're supposed to use the Model API's built-in 'set_x' method.
http://www.djangoproject.com/documentation/models/many_to_many/
Also, are you sure t
Back in middle of last year Adrian Holovaty posted some very helpful
information on how to get the raw output of admin templates for use as
basis for your own views. I'm a newbie trying to get my head around
Django, and it seems the code has been refactored since then. Is it a
simple matter to r
10 matches
Mail list logo
