Thanks looks very helpful. I will look over that when I get a free
moment.
On Apr 9, 10:39 am, Rajesh Dhawan <[EMAIL PROTECTED]> wrote:
> Hi,
>
> On Apr 9, 12:30 am, Chris <[EMAIL PROTECTED]> wrote:
>
> > I am trying create a custom model field that will create 2 field
> > instances, a
Hi,
On Apr 9, 12:30 am, Chris <[EMAIL PROTECTED]> wrote:
> I am trying create a custom model field that will create 2 field
> instances, a CharField and a booleanField. I am using this with
> signals and dispatchers to insert data entered from this custom field
> into another model/table that
I am trying create a custom model field that will create 2 field
instances, a CharField and a booleanField. I am using this with
signals and dispatchers to insert data entered from this custom field
into another model/table that contains a boolean and char field. my
question is: how can I return
Malcolm Tredinnick wrote:
> On Fri, 2007-07-13 at 21:31 -0500, Carl Karsten wrote:
>> I am experimenting with subclassing a model. The parent class will be an
>> abstract class that does not get 'managed' by django. Only the subclass
>> will,
>> and the table the subclass works with will
On Fri, 2007-07-13 at 21:31 -0500, Carl Karsten wrote:
> I am experimenting with subclassing a model. The parent class will be an
> abstract class that does not get 'managed' by django. Only the subclass
> will,
> and the table the subclass works with will have all the fields.
>
> syncdb
Carl Karsten wrote:
> I am experimenting with subclassing a model. The parent class will be an
> abstract class that does not get 'managed' by django. Only the subclass
> will,
> and the table the subclass works with will have all the fields.
>
> syncdb was able to create the table I
I am experimenting with subclassing a model. The parent class will be an
abstract class that does not get 'managed' by django. Only the subclass will,
and the table the subclass works with will have all the fields.
syncdb was able to create the table I expected, the admin let me add and save
On 5/15/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> On Mon, 2007-05-14 at 16:13 -0700, Joe wrote:
> > I was wondering what the status of this is? I know that it broke a
> > while back with the introduction of magic object removal, and has been
> > in the pipeline since. I just tested it
On Mon, 2007-05-14 at 16:13 -0700, Joe wrote:
> I was wondering what the status of this is? I know that it broke a
> while back with the introduction of magic object removal, and has been
> in the pipeline since. I just tested it out on my recent SVN checkout,
> and it seemed to create the tables
I was wondering what the status of this is? I know that it broke a
while back with the introduction of magic object removal, and has been
in the pipeline since. I just tested it out on my recent SVN checkout,
and it seemed to create the tables in the database in the way that one
would expect.
Hello,
I am defining a Product class that gets inherited by various products,
so I am defining in it all the base attributes that exist on all child
products.
I want to know if its possible to forbid changing the actual "products"
table unless you add one of the actual child products.
Also,
Laurent RAHUEL wrote:
> Ooops,
>
> It should be :
>
> class Derived(Parent):
>
> def _pre_save(self):
> do_some_other_things_here
> self.my_method()
>
> Indentation problem ;-)
Thanks Laurent, but there was a typo in my original post !-)
uno desthuilliers a écrit :
>
> Hi,
>
> > hello hello
> >
> > I must be a bit dumb, but I find myself a bit stucked with model
> > subclassing. Here's the problem: how does one call on the superclass
> > method when extending this method in the subc
hello hello
I must be a bit dumb, but I find myself a bit stucked with model
subclassing. Here's the problem: how does one call on the superclass
method when extending this method in the subclass ? ie:
class Parent(meta.Model):
def my_method(self):
do_something_here
class
14 matches
Mail list logo
