Ashesh Vashi 61698b7b4d Do not use the sqlite for session handling, as the old implementation is ... optimized to work from multiple threads. It has too many frequent transaction from multiple threads, and that tends to result into the 'database is locked' error of sqlite. With the new implemenation, we're using the caching mechanism, which keep the data in the memory all the time, and saves it on request completion, and loads it only for the first time. Also, it will storage the data using pickle, which will be faster than accessing sqlite. Fixes #1329		2016-07-08 16:57:46 +05:30
..
driver	Code tidy.	2016-06-21 14:21:06 +01:00
sqlautocomplete	Code tidy.	2016-06-21 14:21:06 +01:00
__init__.py	Code tidy.	2016-06-21 14:21:06 +01:00
ajax.py	Code tidy.	2016-06-21 14:21:06 +01:00
crypto.py	Code tidy.	2016-06-21 14:21:06 +01:00
html.py	[Python 3 compatibility] Introduced a separate HTML safe string function	2016-05-16 11:58:42 +05:30
menu.py	Code tidy.	2016-06-21 14:21:06 +01:00
paths.py	Code tidy.	2016-06-21 14:21:06 +01:00
preferences.py	Code tidy.	2016-06-21 14:21:06 +01:00
route.py	Optimise Python imports.	2016-06-21 14:12:14 +01:00
session.py	Do not use the sqlite for session handling, as the old implementation is	2016-07-08 16:57:46 +05:30