Skipping Cache Invalidations for Unsupported Raw Queries

[git-yogeshkumar]

This is for issue #246
//: # (What're you proposing?)
I am raising a warning if the user is using Raw queries other than direct strings like psycopg2 Compose Objects for execution with cursor, I believe cachalot should not break if such cases are encountered, it should just not invalidate the cache if this happens and let the query execute.

Rationale

Since, raw queries can be executed using multiple formats, we should give users warning and don't raise unhandled exception as it causes unknown issues in running program.

[Andrew-Chen-Wang]

Thanks! Please add a test for this to catch the warning.

[coveralls]

Pull Request Test Coverage Report for Build 6688981804

• 2 of 4 (50.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.3%) to 97.914%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
cachalot/monkey_patch.py	2	4	50.0%

Totals
Change from base Build 6089987763:	-0.3%
Covered Lines:	704
Relevant Lines:	719

---

💛 - Coveralls

[Andrew-Chen-Wang]

thank you!

[Andrew-Chen-Wang]

ci is failing

[git-yogeshkumar]

is there any decorator that I can use to specify test case for a specifc DB only say postgres, cause in this case only postgres support pycopg objects other's don't!

[Andrew-Chen-Wang]

Hi I didn't notice that. You need to support all databases in this case, so I would just write it as plain SQL.

[scorpp]

@git-yogeshkumar I suggest you can use @skipUnless(connection.vendor == 'postgresql', ....) since I'm not aware of other db vendors supporting API like this.

see

django-cachalot/cachalot/tests/postgres.py

Lines 55 to 58 in 6df9704

	@skipUnless(connection.vendor == 'postgresql',
	'This test is only for PostgreSQL')
	@override_settings(USE_TZ=True)
	class PostgresReadTestCase(TestUtilsMixin, TransactionTestCase):