OK, if we can narrow the possibilities down to a patch mistake, I can
tell you what I did:

cywgin
go to django src dir (the 'trunk' directory of svn)
patch -p0 mssql_update5.diff

no errors reported, and TortoiseSVN's icons changed on selected
folders under 'trunk', to indicate code was altered. I took this as
proof the patch has worked ... but honestly, my patching abilities are
almost 0 (i just followed a tutorial, iirc).

My I'll give it another go before bugging you again. Thanks a million!

And yes I'm in continental Europe, so there's a big timezone gap between us.

Best,

On 10/26/06, Sean De La Torre <[EMAIL PROTECTED]> wrote:
>
> Carlos,
>
> This error, "Error: 'inspectdb' isn't supported for the currently
> selected database backend.", is usually thrown when the patch hasn't
> been applied correctly.  Otherwise, you'd see a different error.  Look
> at your <django_install>\django\db\backends\ado_mssql\intropspection.py
> file.  Does the logic in this file match the patch?  If you are not
> sure, attach it to the email and I'll take a look at it.
>
> Sean
>
>
> On 10/25/06, Carlos Yoder <[EMAIL PROTECTED]> wrote:
> >
> > OK, here I go.
> >
> > I'm running the following, from my project's dir. Note: the SQL server
> > is not local, I connect to it via a VPN, and testing it, it works OK,
> > but who knows.
> >
> > D:\dev\eclipse\eclipse_workspace\ceneje>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 
> > name
> > s.
> > #
> > # Also note: You'll have to insert the output of 'django-admin.py 
> > sqlinitialdata
> >  [appname]'
> > # into your database.
> >
> > from django.db import models
> >
> > Error: 'inspectdb' isn't supported for the currently selected database 
> > backend.
> >
> >
> > My settings.py
> >
> > DATABASE_ENGINE = 'ado_mssql'
> > DATABASE_NAME = 'obspm_testing'
> > DATABASE_USER = '*****'
> > DATABASE_PASSWORD = '***'
> > DATABASE_HOST = '192.169.5.8'
> > DATABASE_PORT = '1433'
> >
> > Hope this sheds some light!
> >
> > Best regards and thank you.
> >
> > On 10/26/06, Carlos Yoder <[EMAIL PROTECTED]> wrote:
> > > As soon as I get to the office I'll let you know... thanks for replying!
> > >
> > > > Hmm.  What's the exact error you are getting?  I'm running the code on
> > > > 3 different boxes (2 Win XP Pro and 1 Windows Server 2003) against
> > > > MSDE and SQL Server 2000 without issues.  What system and server are
> > > > you using?
> > > >
> > > > You should be able to use either manage.py in the project directory or
> > > > django-admin.py in the directory below the project directory.
> > > > Remember to run django-admin.py with the --settings option so it knows
> > > > where to look for your settings file.
> > > >
> > > > Sean
> > >
> > > --
> > > Carlos Yoder
> > > http://blog.argentinaslovenia.com/
> > >
> >
> >
> > --
> > Carlos Yoder
> > http://blog.argentinaslovenia.com/
> >
> > >
> >
>
> >
>


-- 
Carlos Yoder
http://blog.argentinaslovenia.com/

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to