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,
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'm glad it worked! Let me know if you run into any other issues.
The more people that look at this patch, the better. The one known
gap in functionality is paging support, but everything else should
work.
On 10/26/06, abc123 <[EMAIL PROTECTED]> wrote:
>
> Hi Sean,
>
> Enthused by your response
Hi Sean,
Enthused by your response, I also deleted my Django install, cleared
out the database, and started from scratch. I installed the latest
version from SVN trunk, patched automatically this time (patch applied
cleanly), and it works fine now.
I went through with diff to see what I'd done w
abc123,
I deleted my Django install and started from scratch. I installed the
latest SVN, applied the patch, and created a new project. I still
didn't see an error, so I'm thinking that the problem could be one of
two things:
1. There's a problem with MSSQL 2005
2. A portion of the patch wasn'
No, not really. There have been other users successfully using the
patch against SQL Server 2000. I haven't run into anyone using SQL
Server 2005 yet, so I'm interested in seeing if this is a problem
specific to that version.
Sean
On 10/26/06, Carlos Yoder <[EMAIL PROTECTED]> wrote:
>
> Looks
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\db\backends\ado_mssql\intropspection.py
file. Does the logic in th
Looks like both abc123 and myself are experiencing the same problem
(at least one of them). Since I'm running MSSQL2000, wouldn't this
rule out MSSQL2005 being the problem?
Carlos
On 10/26/06, abc123 <[EMAIL PROTECTED]> wrote:
>
> Sean De La Torre wrote:
> > Can you post the entire traceback? I
Sean De La Torre wrote:
> Can you post the entire traceback? I don't see this behavior with SQL
> Server 2000 or MSDE. I may have to get a copy of SQL Server 2005.
I can, the full traceback is rather long:
E:\test>python manage.py syncdb
# Note: Any fields that are named 'id', are of type 'Aut
I forgot to state my config.
I'm running Django in my dev box, on Windows 2000 Pro. The server is
running Windows 2003 Server, located elsewhere, accessed transparently
via a secure VPN thru standard port 1433.
Plus, I've been trying two more things:
1. Create an empty database, create some mod
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
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
Can you post the entire traceback? I don't see this behavior with SQL
Server 2000 or MSDE. I may have to get a copy of SQL Server 2005.
I'll also try using the latest Django version from the trunk - my
production installation is the current official Django release (0.95)
modified with the patch
Hello Sean,
I'm also trying this; I've updated from SVN recently (a week or so
ago), then applied ticket 2358 diff 5 (by hand, but I have checked it
more than once), and am running against SQL Server 2005.
Starting from scratch, I can run python manage.py syncdb, and get some
tables inserted int
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-a
I'm afraid I already applied that patch. Actually I tried many
combinations but no luck.
I'm running (from the project's directory, where settings.py is)
"manage.py inspectdb". Maybe that's the problem, and I must absolutely
run it from django-admin.py ?
I admin this just crossed my mind, when i
Take a look at this ticket: http://code.djangoproject.com/ticket/2358.
I combined that previous patch (2563) with 2358 because my patch was
dependent on it. Make sure that you've applied the latest patch
(mssql_update5.diff) to your Django installation. If you still have
problems, please let me
Hey Sean, I'm trying to give this a go. Running into walls, I'm afraid.
I read 'introspection' and thought this patched "manage.py inspectdb"
to handle mssql servers. Unless I did something wrong (very possible),
that doesn't seem to work.
Could you explain how do I get to the 'full instrospect
Sorry for the double-post :)On 8/25/06, Sean De La Torre <[EMAIL PROTECTED]> wrote:
I've posted a patch that adds full introspection functionality forado_mssql backends (http://code.djangoproject.com/ticket/2563). I'dappreciate it if those of you who run Django/mssql could test it out
and let me k
19 matches
Mail list logo
