Sean,
Good news!
I major blunder on my side. I was updating from SVN all the time, but
happily ignoring that install, since Python was 'seeing' and old stale
egg on site-packages. I removed everything, and svn'd from tunk
directly on site-packages, and voila. =)
Now I have a different problem, which I believe it could be a bug.
When inspecting my DB, which has a table called 'ADMIN', the indexing
part fails, with the following:
class Admin(models.Model):
Traceback (most recent call last):
File "D:\dev\eclipse\eclipse_workspace\ceneje\manage.py", line 11, in ?
execute_manager(settings)
File "D:\dev\Python23\lib\site-packages\django\core\management.py", line 1445,
in execute_manager
execute_from_command_line(action_mapping, argv)
File "D:\dev\Python23\lib\site-packages\django\core\management.py", line 1356,
in execute_from_command_line
for line in action_mapping[action]():
File "D:\dev\Python23\lib\site-packages\django\core\management.py", line 764,
in inspectdb
indexes = introspection_module.get_indexes(cursor, table_name)
File "D:\dev\Python23\lib\site-packages\django\db\backends\ado_mssql\introspec
tion.py", line 97, in get_indexes
results.update(data)
AttributeError: keys
The first output line is class Admin(models.Model), and that should
point towards the fact that it could be a reserved name collision of
some sort. I'll try with a different test database, and also
temporarily renaming that ADMIN table, etc.
Thanks a lot! I'll keep you posted,
Carlos
On 10/27/06, Carlos Yoder <[EMAIL PROTECTED]> wrote:
> 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/
>
--
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
-~----------~----~----~----~------~----~------~--~---
