A little tip
Just a little tip for when designing databases in MySQL.
Do NOT name fields to "read","write" or "delete".
I'm working on a mediabank project where I wan't to set permissions to each user for every object that is being created. The permissions are, as you might figure out, read/write/delete. But MySQL return a 1064 error when executing a query like "select userId from objectaccess where read=1".
I think have to drink more coffee before I start to code the next time.... =)
Do NOT name fields to "read","write" or "delete".
I'm working on a mediabank project where I wan't to set permissions to each user for every object that is being created. The permissions are, as you might figure out, read/write/delete. But MySQL return a 1064 error when executing a query like "select userId from objectaccess where read=1".
I think have to drink more coffee before I start to code the next time.... =)

Detta är min alldeles högst personliga blogg där jag skriver om än det ena än det andra.
Ibland skriver jag ofta(re) ibland väldigt sällan. Jag skriver delvis säsongsbetonat då jag är ett stort Formel 1-fan och delvis om mitt jobb/hobby som programmerare. Mer om mig hittar du 

Kommentarer
If you aren't familiar with the process you make constants for the values in this manner:
read = 2^0
write = 2^1
delete = 2^2
When you want to set a value you or it in.
When you want to check if it's set you use bitwise AND and when you want to unset it you use bitwise XOR.
Select limit from ... blir massa med fel =)
Men egentligen bör man hålla sig inom ramarna och låta bli att döpa tabeller och fält efter de reserverade orden.