Fix some column types being parsed twice

[pmdevita]

After the SQLAlchemy 2.0 fixes, ormar's test suite highlighted a problem with JSON and enum types getting parsed from the database a second time. This should fix the problem. I'm not sure if there are any other data types affected at the moment, it should hopefully be just these two. I've also added appropriate tests for these data types.

Let me know if I need to change anything, thanks!

[tarsil]

After the SQLAlchemy 2.0 fixes, ormar's test suite highlighted a problem with JSON and enum types getting parsed from the database a second time. This should fix the problem. I'm not sure if there are any other data types affected at the moment, it should hopefully be just these two. I've also added appropriate tests for these data types.

Let me know if I need to change anything, thanks!

This looks ok to me. Let us get a second opinion on this while I also check it.

Thank you for the submission.

[pmdevita]

TIME also needed to be fixed, added a test for it along with DATE

EDIT: OK custom types on the Postgres backend were also being affected. I've changed the logic to be inclusive rather than exclusive. Only primitive types with a Postgres backend are processed now.

[tarsil]

@Kludex I did some research and SQLA did some internal changes after the version 2.0.24 and I'm actually happy with these changes as well. If you agree, we can move forward.

[Kludex]

Feel the owner here. I trust you.

[tarsil]

@pmdevita thank you for your submission here as it was a nice catch from ormar. So far the changes you have applied, it seems like its covering the scenarios properly.