Read Query Handler returns null about slim-api-skeleton HOT 11 CLOSED

How does the migration file for entries table look like? To me it seems like the timestamp columns are not created or they are not auto updating.

from slim-api-skeleton.

I haven't touched the migration file. I copied the todos table to the entries one using phpmyadmin. Should I be creating the entries table using the migration file? Is there a way not to do so?

from slim-api-skeleton.

Using PHPMyAdmin look at the entries table you created. Are the timestamps created and do they have meaningful values, ie are the created_at and updated_at columns there and do they have values or are they null?

from slim-api-skeleton.

Yes all the timestamps look okay and they are exactly as the todos table was.

from slim-api-skeleton.

I've also created new entryRepository and ZendEntryRepository classes that's used for the handlers in the commandBus.

from slim-api-skeleton.

Ok. It seems data from database is not hydrated into the Entry object. Look at the ZendEntryRepository and EntryHydratorFactory you have created and compare them to the working Todo ones from the skeleton.

from slim-api-skeleton.

Thanks. They're virtually the same except that all Todo and todo strings were replaced with Entry and entry.

Any other suggestions?

Thanks so far BTW. You're great!

from slim-api-skeleton.

I've rerun the migration and added the entries table, which is exactly the same as todos except for the table name.

Now I'm getting NULL on the entries GET request as well, instead of an empty array... any ideas?

from slim-api-skeleton.

Not really. Try to compare to everything to how it is done with the original Todo's.

from slim-api-skeleton.

OK I figured the issue out!

I had the ZendEntryRepository options set to ['buffer_results' => true]. I had added that thinking it might come in useful due to the bug reported in #39.

Now I wonder how to solve the issue of running consecutive queries moving forward?

from slim-api-skeleton.

Sorry if I wasn't clear enough, but removing ['buffer_results' => true] fixed the issue.

from slim-api-skeleton.