that's the point
On Fri, May 22, 2009 at 4:30 PM, Daniel Roseman <
roseman.dan...@googlemail.com> wrote:
>
> On May 22, 6:19 am, vishy wrote:
> > Hi,
> >
> > I have some functionality which needs to be part of a class,which I
> > don't want to persist in database.Where should I put such a class?
On May 22, 6:19 am, vishy wrote:
> Hi,
>
> I have some functionality which needs to be part of a class,which I
> don't want to persist in database.Where should I put such a class? In
> models.py?
You can put it anywhere on your pythonpath. If it's related to a
single application, you might try t
Maybe it is . you can see the sourcecode of django ,some models have
the methods to add some functionalities .
but I really do not know if it is right or not ...
On 5/22/09, vishy wrote:
>
> Hi,
>
> I have some functionality which needs to be part of a class,which I
> don't want to pe
Hi,
I have some functionality which needs to be part of a class,which I
don't want to persist in database.Where should I put such a class? In
models.py?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users"
4 matches
Mail list logo