First of all, which version of Geeklog are you using? That error may have been fixed in 1.3.7.
Also, please quote the corresponding error message from your logs/error.log file. It will include the actual SQL request that caused the problem. This will help us see where the actual problem is ...
bye, Dirk