On Mon, 2007-06-11 at 15:07 -0500, Carl Karsten wrote:
> If I were starting from scratch, I would use MySql. But currently there is a 
> db 
> model in MsSql.   the 2 affections to mssql is 1: it is what the client has 
> (so 
> I don't have to sell them on anyting new) and 2) it is where the model 
> currently 
> is.     The plan is to see how far I can get with Ms, if I run into bumps 
> submit 
> track tickets.  if the path gets too bumpy, switch to MySql.
> 
> I have hit my first bump:
> 
> settings.py DATABASE_ENGINE = 'ado_mssql'
> and the rest of the stuff to connect to my db.
> manage.py inspectdb
> 
> # This is an auto-generated Django model module.
> # You'll have to do the following manually to clean this up:
> #     * Rearrange models' order
> #     * Make sure each model has one field with primary_key=True
> # Feel free to rename the models, but don't rename db_table values or field 
> names.
> #
> # Also note: You'll have to insert the output of 'django-admin.py sqlcustom 
> [appname]'
> # into your database.
>   from django.db import models
>   Error: 'inspectdb' isn't supported for the currently selected database 
> backend.
> 
> I have done introspection using odbc, and I have generated CREATE commands, 
> so I 
> might be able to help get something working here.  Has anyone started working 
> on 
> this?  If not, can someone point me to where I should start so I don't have 
> to 
> trace too much.

Have a look at tickets #1412 and #3702 (basically, search for ado_mssql
in Trac). As you can see, there's been some work done there, although by
the admission of the guy who's done the bulk of the work, they aren't
complete yet.

At the moment, we have been reluctant to add ado_mssql back into
Django's "supported" pile, because nobody has stepped up and
demonstrated commitment to keep it maintained (which requires an actual
demonstration of said commitment, not just an expression of intent).

Getting those patches into some sort of completed state would be a good
job, if you had the time.

Alternatively, if you just want to be a user for the moment, the stuff
in #3702, particularly, is probably of some use to you.

Regards,
Malcolm



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to