On Oct 19, 10:10 pm, Carl Meyer <[EMAIL PROTECTED]> wrote:
> Just ran into this issue myself (first time using non-abstract
> inheritance). The catch with this recipe is that you can never save a
> derived object from a parent instance, or you break the final_type
> field (it will then contain th
Hi all,
A little while ago, I needed to write a number of simple static
websites. I would have done everything in pure HTML if it would not
have been for the site navigation: adding a single page would have
forced me to edit the menu of all existing pages. It was clear that
the pure HTML approach
Hi,
great to see the release of version 1.0 !!!
I was wondering if per-object-level (aka row-level) permissions have
been included into this release. if not, is there any plan to include
them, or is there any work-around/third-party project that works
together with the new version?
thanks!
- ha
Dear all,
I am playing around with model inheritance introduced in django 1.0.
In particular, I am trying to achieve something that might be called
dynamic-casts (with reference to C++). Consider the following example
type hierarchy:
MediaObject
|
+-- ImageObject
| |
| +
> > I was wondering if per-object-level (aka row-level) permissions have
> > been included into this release.
> > if not, is there any plan to include
> > them,
>
> You say "them" as if there's an existing working addition to Django that
> supports this and is in some way the obviously correct wa
> It does not work at all. For some reason, final_type also gets
> upcasted to MediaObject?!
I found the solution, now. The problem was that the __init__ method of
a Model is also called when objects are restored from the database. So
when the base class gets initialized by the QueryManager, it
o
Hi Malcolm,
Malcolm Tredinnick wrote:
> > class BaseClass(models.Model) :
> > final_type = models.ForeignKey(ContentType)
> >
> > def save(self,*args) :
>
> For absolute robustness, you should also accept **kwargs here. There are
> a couple of places in Django's code that will
Dear list,
I have two models that are in the following relationship:
class Member(django.contrib.auth.models.User) :
# some app specific stuff here
pass
class Event(django.db.models.Model) :
attendees = models.ManyToManyRelation(Member)
# some other fields
In my
Thanks for the pointers. This is exactly what I want and have to do
then ... fingers crossed for inclusion into django1.2!
On Nov 17, 5:15 pm, Tom Evans wrote:
> On Tue, Nov 17, 2009 at 4:07 PM, dadapapa wrote:
> > Dear list,
>
> > I have two models that are in the foll
Dear list,
I am using Django 1.0 + MySQL on the production server and Django 1.1
+ sqlite3 on my (local) development server. My application uses
contrib.auth.User etc. and I am running into the following issue when
trying to migrate the production database to the development server.
production se
I managed to solve the problem. The solution is to explicitly state
the applications (models) that you want to migrate, and leave out
those that get initialized automatically when doing syncdb
(contenttypes). Here's how it worked for me:
production server:
$ python manage.py dumpdata auth custom_a
11 matches
Mail list logo
