Seems like Joseph's problem is typical for User/Profile work.
Initially I used the same inheritance model as he does. Working with a
single form in the view and template is a win for code re-use and
simplicity.
I looked into formsets but haven't gotten it to work with multiple
model types. It se
yo,
This isn't strictly django related, but anyone using sqlite3
underneath might encounter this problem:
"Adding index changes LEFT OUTER JOIN to act as INNER JOIN"
from ticket 3015 in the sqlite bug tracker
http://www.sqlite.org/cvstrac/tktview?tn=3015,10
It's been fixed in the repo but not
ate. Regardless, it helps to
have a clearer picture of what's going!
ps - The following sql command list is super useful. Props to the
author.
http://www.pantz.org/software/mysql/mysqlcommands.html
I hope that helps,
diN0bot!
Are you an awesome open source developer who loves
3 matches
Mail list logo
