Re: Best practice on data security .. on record, table (model) db or url

I did find a nice sidewide middleware login system which takes care of one aspect of my 'problem'. http://www.djangosnippets.org/snippets/1158/ Not completely to my taste, because it (me?) requires some css file in PUBLIC_URLS. Figured I'd start on the manual @login_required for now to get som

Re: Best practice on data security .. on record, table (model) db or url

2009/8/21 Gerard : > > Hi All, > > I'm working on an invoice system, currently deployed the single user version >  in house. Next one is gonna be a full blown multi user setup. Having > fairly good knowledge of security, I was wondering what would be best > practice in Django for data separation.

Best practice on data security .. on record, table (model) db or url

Hi All, I'm working on an invoice system, currently deployed the single user version in house. Next one is gonna be a full blown multi user setup. Having fairly good knowledge of security, I was wondering what would be best practice in Django for data separation. So user A only sees his cust