On Sun, Jan 25, 2009 at 2:14 AM, Adi Sieker wrote:
>
> Hi,
>
> as far as I know loaddata doesn't use the ORM to insert the data.
Incorrect. loaddata does use the ORM, but it uses raw save mode, which
disables custom save methods. Raw save mode also disables any database
field pre-handling, such
Hi,
as far as I know loaddata doesn't use the ORM to insert the data.
So things like signals and overloaded save methods don't work when
using loaddata.
adi
On 24.01.2009, at 17:48, Kless wrote:
>
>
>
> On 24 ene, 15:51, Daniel Roseman
> wrote:
>> Are you saying that the slug is not being cre
On 24 ene, 15:51, Daniel Roseman
wrote:
> Are you saying that the slug is not being created when you reload your
> previously dumped data via ./manage.py loaddata? This is expected
> behaviour.
Yes, that's it.
The slug is succesfully created when a new objects is added but it
doesn't works sin
On Jan 24, 12:49 pm, Kless wrote:
> I want to add a new field --slug-- to tables where any data is being
> used in the URL
>
> I dumped all data, added that new field
> --
> slug = models.SlugField(_('slug'))
> --
>
> And I created a hook to save it.
> --
> def save(self):
4 matches
Mail list logo