On Fri, May 16, 2008 at 3:18 PM, Carlos Hanson <[EMAIL PROTECTED]> wrote:
> On Fri, May 16, 2008 at 10:49 AM, Jim Steil <[EMAIL PROTECTED]> wrote:
>> Carlos Hanson wrote:
>> On Fri, May 16, 2008 at 8:14 AM, Michael Bayer <[EMAIL PROTECTED]>
>> wrote:
>> On May 16, 2008, at 10:55 AM, Carlos Hanson wrote:
>> On Fri, May 16, 2008 at 6:13 AM, Jim Steil <[EMAIL PROTECTED]> wrote:
>>
>> Hi:
>>
>> Can anyone tell me if it is possible to access data on an AS/400
>> through
>> SQLAlchemy?
>>
>>   -Jim
>>

It's possible if you use db2 connect to make your connection to the
iSeries.  See http://code.google.com/p/ibm-db/.  The support group is
[EMAIL PROTECTED]

Right now, the as/400 is listed as a "Future supported database" [1],
but there have been some reports from people getting it working.  You
might want to make your needs known on the support list & also follow
up with your IBM rep.

[1] http://code.google.com/p/ibm-db/wiki/README


>>
>> I'm connecting to an AS/400 using pyodbc, so I am sure that I can do
>> it through SQLAlchemy.  If I have a chances to test it, I'll post my
>> success.  But if you get an ODBC connection set up, the re should be
>> no problem.
>>
>>
>> well, "connecting" is just the beginning.  to take advantage of SQLA,
>> you would also want an AS/400 dialect that knows how to render SQL in
>> the way an AS/400 likes.  Im not familiar with anyone working on an AS/
>> 400 dialect at the moment.   I only know of the DB2 dialect which is a
>> separate project (but maybe ask on their list since they work for IBM).
>>
>>
>> This is a good point. I have to create aliases to a file/member
>> combination to select data. I guess I wouldn't expect SQLAlchemy to
>> implement that by default, since most every other database uses
>> tables.
>>

Right... but there's no reason you can't drop down to the db-api level
for one-off things like partitioning data with "members".   Once the
alias is created, it can be treated like any other table.

-ken

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to