|
Hi guys, When posting a new question to my new installation of OSQA I'm getting the following error:
I'm using the django-mssql provider, but I'm not sure the problem lies there. It seems for some reason the ORM is trying to update the id (with the same value it searches on). Any ideas why this might be? as far as I can establish other routines work fine (such as creating new users). This is on the latest version in the trunk. Thanks
showing 5 of 6
show 1 more comments
|
|
I'm very new to both Python and Django. Please correct me or offer suggestions if there is a better way, but I was able to work around this by patching _get_update_kwargs() in forum/models/base.py. Original
Patched
|
just tried using the mysql provider and that one seems to work fine? perhaps there's an issue with the way MySQL and SQL Server deal with identity columns? or is it just an issue with the django-mssql project>
I would file a bug report with the django-mssql project. We haven't done extensive testing with SQL Server, but our code should be relatively portable.
The link to the opened issue:
I can't see the link ... hopefully this will work: http://code.google.com/p/django-mssql/issues/detail?id=90 ... if not: it's simply ID 90 ;-)
Is this still relevant? How about opening a bug in jira.osqa.net? (I know it might not be an OSQA issue, but I think it's important to have this documented as a bug, because it affects OSQA users).
@ripper234 Yes, this issue is still relevant. It doesn't look like anything has been done with issue 90 in django-mssql