On 10/14/05, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> * Run the Django unit tests with SQL Server as the backend. Just run
> tests/runtests.py ...
> The more eyes we get on this one, the sooner we can make sure it's
> solid. Thanks for any help!
I have Sql Server at work, and can test this e
Access to SQL Server is always a problem. :-)
1) MSDE 2000 (http://www.microsoft.com/sql/msde/default.mspx)
"Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) is the free,
redistributable version of SQL Server that's ideal for client applications
that require an embedded database, new devel
As of revision 879, I've added experimental support for MS SQL Server
database backends, thanks to a patch from [EMAIL PROTECTED]
To use it, just change your DATABASE_ENGINE setting to "ado_mssql".
I don't have access to SQL Server, so I haven't been able to test it.
I have no idea how well it w
On 10/14/05, jws <[EMAIL PROTECTED]> wrote:
> I'd like to use Django for a project I am currently bidding on, but I
> need to know if MSSQL support will eventually be mainlined. I can
> tolerate some patchy-ness in the short term, but I don't want to
> maintain a parallel codebase for years, espec
On 10/14/05, Joseph Kocherhans <[EMAIL PROTECTED]> wrote:
> Just submitted a patch that does exactly that.
> http://code.djangoproject.com/ticket/628
As of revision 878, it's an official part of Django. Thanks!
Adrian
--
Adrian Holovaty
holovaty.com | djangoproject.com | chicagocrime.org
On 10/10/05, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> On 10/10/05, Joseph Kocherhans <[EMAIL PROTECTED]> wrote:
> > I'd like to use doctest for testing my model classes, but the model
> > metaclass overwrites my classes docstrings. Is there any reason why it
> > MUST override __doc__? I thin
Is anyone working on support for MS SQL Server? I've seen people
discuss it in the past, but have heard nothing specific regarding
'official' support. There's the following entry in the wiki, but
nothing more seems to be happening.
http://code.djangoproject.com/ticket/225
I'd like to use Django
[EMAIL PROTECTED] wrote:
> ... transaction support, its the biggest thing stopping me from using
> django for production work.
Me, too. I'd like to use Django for a time and expense app, but it's a
no go without some kind of answer for bootstrapping transactions into
my code.
-jason
Hi,
>Maybe it would be easier to discuss this with some code at hand. If
>#616 would be applied, django would have the needed "process_exception"
>mechanism (that would be usefull regardless wether we use it for
>transactions or not, I think). Then I could hack up the middleware and
>decorator as
fwiw the zope transaction implementation supports save points from data
managers that support it. the postgres impl currently doesn't but it
would be straightforward to make it so.
cheers,
-kapil
fwiw, the architecture of the patch, allows for that use case, the zope
transaction library defines a transaction manager, with apis for
retrieving transaction objects and manipulating them and some convience
items for commiting, aborting directly from the manager. data managers
are objects that r
the transaction patch didn't couple the transactions exclusively to the
web layer, with it you can use a python script or interactive
interpreter, via the api provided by the transaction manager. ie.
import transaction
# do some work
# and
transaction.commit()
# or
transaction.abort()
additiona
cool, just noticed this and i'm really glad to see the discussion of
transaction support, its the biggest thing stopping me from using
django for production work.
regarding the patch, i'll address the transaction coupling in another
respone in this thread, but the zope usage, i wanted to clarify.
13 matches
Mail list logo