Yes thanks
(null)
El El mar, 5 de dic de 2023 a la(s) 13:41, dilo...@gmail.com <
dilou...@gmail.com> escribió:
> HelloI am running into the same problem but I do not understand what needs
> to be done. I use keepdb but how can I get the database cursor connection.
> Do I need to modify the
HelloI am running into the same problem but I do not understand what needs
to be done. I use keepdb but how can I get the database cursor connection.
Do I need to modify the test script?
Thanks for your help.
Le mercredi 13 février 2019 à 10:54:04 UTC+1, Anton Melser a écrit :
> When you use
>
> When you use django unittests commit is made as no-op. Use --keepdb and at
> the end of your tests run SQL commit against your database cursor
> connection.
>
Awesome, exactly the info I was missing. Thanks for your help.
Cheers,
Anton
--
You received this message because you are subscribed
When you use django unittests commit is made as no-op. Use --keepdb and at
the end of your tests run SQL commit against your database cursor
connection.
On Wed, Feb 13, 2019 at 5:54 AM Anton Melser wrote:
> Hi,
>
> I can't work out whether it is expected or whether I am missing something.
> I
Have you looked at fixtures?
manage.py dumpdata will create a json file from a database. I use it to
populate the test database from production data reference tables. dumpdata
let's you --exclude=... the other tables.
I know that's not exactly what you asked for but maybe you can import data
Hi,
I can't work out whether it is expected or whether I am missing something.
I would like to keep the DB data that I generate during a test run to
inspect/persist it. --keepdb means I have empty tables at the end,
strangely even if I ctrl-C a test run. It would also be logical for test
data
6 matches
Mail list logo
