InvalidArgumentException: "App\DataFixtures\UserFixtures" is not a registered fixture about liiptestfixturesbundle

[alexislefebvre]

Please try these suggestions: #57 (comment)

[dubitoph]

Hello, I don't understand what I must try because my fixtures are in the src/Datafixtures repository.

[dubitoph]

In the fixture, I changed the Doctrine\Common\DataFixtures\FixtureInterface implementation to Doctrine\Common\DataFixtures\AbstractFixture implementation. I don't have anymore the previously error, but the data aren't saved in the database.

[alexislefebvre]

You need to persist data: https://symfony.com/doc/3.0/bundles/DoctrineFixturesBundle/index.html#writing-fixtures

Add this for every entity:

$manager->persist($user);
$manager->flush();

[dubitoph]

Of course! Really sorry for this mistake on my part and thank you very much for your help.

[vulkanosaure]

Add this for every entity:
$manager->persist($user);
$manager->flush();

are you saying that we need to flush inside the loop ?
flush is designed to be called only once at the end, or isn't that what you meant ?

edit : I also saw an article where someone was flushing in the loop, so I'm really curious if there is something i don't know about.
I don't wanna do it unless it's really necessary since that sounds like a waste of resource.

[alexislefebvre]

@vulkanosaure you can call flush() only once, it should work.

If you add tens or hundreds of entities, check the doc about Batch Processing: https://www.doctrine-project.org/projects/doctrine-orm/en/2.16/reference/batch-processing.html

See also this answer on Stack Overflow: https://stackoverflow.com/a/21335487/2257664 (spoiler: it's mine 😁)

[vulkanosaure]

thanks but why isn't using one single flush for a hundred of entities recommended ?
is it slower than the batch process you describe ? (eg: 10 flush that each handle 10 persist)

[alexislefebvre]

Adding hundreds of records then:

• using only flush at the end may use a lot of RAM (hydrated entities can be pretty heavy). If I remember correctly Doctrine had performance issues when dealing with thousand of entities and the final flush was slow. It was about 10 years ago though so it may be better now
• using flush on every iteration of the loop may be slower since it will perform many requests

Between these 2 cases, batch processing is a trade-off and it can help to not overwhelm Doctrine. It depends on the amount of data to be stored, so the first step is to test and see if you encounter performance issues, if that's the case then you can try different sizes for the batch. If you have no slowness when adding entities, keep one flush and move along.

[vulkanosaure]

ok, thanks for the insights !

[vulkanosaure]

by the way, while i'm here :) from my understanding, we always have to define our fixture in a separate class, what i would really like is to define the fixture data inside my test function, (maybe not always but at least sometimes) i really like the idea of having a tight coupling between a test and the specific data it requires, to avoid creating some kind of global state that will be likely to break at scale. Is there any way to achieve that with your lib ? something like $this->databaseTool->loadFixturesInline(function(){ //define fixture code here... }); Thanks

…

On Wed, Nov 8, 2023 at 6:30 PM Alexis Lefebvre ***@***.***> wrote: Adding hundreds of records then: - using only flush at the end may use a lot of RAM (hydrated entities can be pretty heavy). If I remember correctly Doctrine had performance issues when dealing with thousand of entities and the final flush was slow. It was about 10 years ago though so it may be better now - using flush on every iteration of the loop may be slower since it will perform many requests Between these 2 cases, batch processing is a trade-off and it can help to not overwhelm Doctrine. It depends on the amount of data to be stored, so the first step is to test and see if you encounter performance issues. If you have no slowness when adding entities, keep one flush. — Reply to this email directly, view it on GitHub <#64 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABGJ2XBPQHABG5QD6FPZVMLYDNUNHAVCNFSM4MTXPGP2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBQGE3TAMZSHA3A> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- *Vincent Huss* *Développeur Fullstack | *Symfony - Angular - Ionic *([phone] | **skype : *vincent.huss * | * *website : * www.appinstrasbourg.com <http://appinstrasbourg.com/>

[alexislefebvre]

@vulkanosaure Let's discuss this there:

• #245