On Sun, Oct 25, 2009 at 05:05:30AM -0700, Vernon Cole wrote:
>
>I have been thinking About this in re STORM too. Perhaps the best way
>would be like:
>
>Try:
>Import prefferedDb as db
>Db.version = 'native'
>Except:
>Import adodbapi as db
># then later if needed
>If db.version = 'native
Windows Mobile phone
-Original Message-
From: Markus Törnqvist
Sent: Saturday, October 24, 2009 2:58 AM
To: Discussion of IronPython
Subject: Re: [IronPython] Database Engine for Django on IronPython
On Fri, Oct 23, 2009 at 04:36:27PM -0600, Vernon Cole wrote:
>
>So it would appear that
On Fri, Oct 23, 2009 at 04:36:27PM -0600, Vernon Cole wrote:
>
>So it would appear that if I always use the OleDb provider, then I always
>have qmark parameter style, even if I am opening an Oracle data base. The
>conversion from pyformat to qmark would be done programatically in adodbapi.
>There m
Good question. It made me look up the documentation. The answer is a
definite "sometimes". I have always used the OleDb client, so I have only
experienced the qmark. I quote from the Microsoft documentation
V V V V V V V V V V V V V V V V V V V V V
The syntax for parameter placeholders d
Vernon Cole wrote:
"The big thing will be paramstyle format convertion. MS-SQL uses qmark.
I am told that django wants pyformat."
Quick question. Is this new database driver going to be specific to
MS-SQL, or does the ADO.NET specification specify qmark in place of
Pyformat?
The reason I
On Fri, Oct 23, 2009 at 12:41:21PM -0600, Vernon Cole wrote:
>Okay, it's officially on top of my to-do list. I try to dedicate an hour or
>two each day to open source projects, so this will keep me busy for a
>while.
If there's anything I can do to help, just ask :)
>The big thing will be param
Okay, it's officially on top of my to-do list. I try to dedicate an hour or
two each day to open source projects, so this will keep me busy for a
while. The big thing will be paramstyle format convertion. MS-SQL uses
qmark. I am told that django wants pyformat. Somebody *please* correct me
if t
2009/10/23 Markus Törnqvist :
>
> So it's not only me who'd be grateful, tho it seems I'm the only guy on
> the list :>
I would be grateful, and I think a lot developers at MS-only shops
would be too - it's just that those programmers tend to be the silent
type, sadly. It's easy for Django to plug
On Fri, Oct 23, 2009 at 11:45:46AM -0600, Vernon Cole wrote:
>The sourceforge download will work out of the box on Iron Python, but it is
>missing a bunch of django special tweaks that they made after they forked
>off their own version -- which was *before* I added Iron Python support. If
>you are
The sourceforge download will work out of the box on Iron Python, but it is
missing a bunch of django special tweaks that they made after they forked
off their own version -- which was *before* I added Iron Python support. If
you are serious about this project, I am willing to go to work to back p
On Fri, Oct 23, 2009 at 08:45:03AM -0600, Vernon Cole wrote:
>Markus:
> What database engine are you using? I am also interested in this project
>and would like to help out.
MSSQL.
I hacked something together called kludgemssql and it probably doesn't
work, but I'm having a hard time testing it
11 matches
Mail list logo
