Yep, here's one for MS-SQL 2000:
http://www.microsoft.com/downloads/details.aspx?FamilyID=413744d1-a0bc-479f-bafa-e4b278eb9147&DisplayLang=en
There's one for the new version as well
(http://www.microsoft.com/sql/editions/express/default.mspx), but I
wouldn't think that it's widely deployed yet,
is there a free developer version of MS-SQL out there ? runs on XP perhaps ?On Apr 3, 2006, at 6:36 PM, Rick Morrison wrote:Sure, for example, previous version failed the DateTest in testtypes.py; issuing the SELECT with no FROM clause. Thanks for rolling it in. Rick On 4/3/06, Michael Bayer <[
Sure, for example, previous version failed the DateTest in testtypes.py; issuing the SELECT with no FROM clause.
Thanks for rolling it in.
Rick
On 4/3/06, Michael Bayer <[EMAIL PROTECTED]> wrote:
Rick -it passes the
same unit tests I was using, so if it works for other cases I didnt try
(since I
Rick -it passes the same unit tests I was using, so if it works for other cases I didnt try (since I hardly tried any), great (can you produce a unit test that fails with the previous version? not so crucial tho). committed in rev 1254.- mikeOn Apr 3, 2006, at 5:12 PM, Rick Morrison wrote:Didn't w
Didn't work for me, Mike -- didn't generate FROM clauses at all for normal non-aliased, same-schema SELECT queries.
Did you maybe mean this way? (clean patch also attached).
def visit_table(self, table):
# alias schema-qualified tables
- if self.tablealiases.has_key(table):
OH...um, why yes it is ! as of 15 seconds ago. enjoy !
On Apr 3, 2006, at 5:40 AM, Michael Twomey wrote:
On 4/3/06, Michael Bayer <[EMAIL PROTECTED]> wrote:
i committed the whole thing with a working version of the Alias
thing i
Hi Rick and Michael,
Thanks for adding mssql support, I've
On 4/3/06, Michael Bayer <[EMAIL PROTECTED]> wrote:
> i committed the whole thing with a working version of the Alias thing i
Hi Rick and Michael,
Thanks for adding mssql support, I've been dying to try out sqlalchemy
on some of my work servers. One thing though, I can't find mssql.py in
the late
hey rick -
i committed the whole thing with a working version of the Alias thing i
mentioned, and it seems to work fine, as far as forming that SQL properly
( i tested it by switching the "engine" at the top of test/select.py to
create_engine('mssql')).
so give the whole thing a go with an actua
Hmm, now that you mention it, you're rightI wonder why the way I'm doing it now works, seems like it shouldn't.I'll look into this.RickOn 4/1/06,
Michael Bayer <[EMAIL PROTECTED]> wrote:
rick -if you need SELECT .colname FROM schema.table AS , then you will have to translate more than just the
rick -if you need SELECT .colname FROM schema.table AS , then you will have to translate more than just the FROM output, you need to translate the column clause elements also. so it might work better to actually create a real Alias to do the work (this is a rough idea...probably needs some tweakin
I'm not sure I've got all of the cases covered, but at least one instance is this:SQL Server seems to need a table name to be aliased when it is referenced in a different schema, so SELECT otherschema.tablename.columnname
FROM otherschemaname.tablenamewon't work, and instead needs to be specified
rick -
this is terrific, I will try to commit this ASAP.
Since I dont have an MS-SQL server to test here, can you show me an
example of what special treatment it needs for "tablename AS alias", where
there needs to be an "AS" thats not already there ? I noticed theres some
extra stuff in there
The attached patch implements a Microsoft SQL Server engine for Sql Alchemy.
This module passes most unitests, but is still in a fairly early stage and should be considered for experimental use only.
Thanks to Runar Petursson for earlier work on this module.
Rick
Release notes
---
13 matches
Mail list logo
