Re: [Ironpython-users] DataSet --> SQLite

2012-03-14 Thread Vernon Cole
I would suggest opening both databases in their native form, then do the comparison using Python code rather than a complex SQL query. It may take a while to run, but should work okay. SQLite select statements are quite fast. Trying to do the whole thing in one swallow may be too much. Better to do

[Ironpython-users] IronPython, Daily Digest 3/13/2012

2012-03-14 Thread no_reply
Hi ironpython, Here's your Daily Digest of new issues for project "IronPython". In today's digest:ISSUES 1. [Status update] sys.version_info < tuple doesn't work like CPython 2. [New issue] ctypes: wrong value returned for c_char_Array 3. [New comment] NullReference bug report 4. [New comment] N

Re: [Ironpython-users] __future__.py

2012-03-14 Thread Dino Viehland
The historic reason is that we supported running both w/ the std lib and without. I don't think that's really a concern so the fake __future__ could be replaced with the real one from the std lib. From: [email protected] [mailto:ironpython-users-bounces+di

[Ironpython-users] DataSet --> SQLite

2012-03-14 Thread Sven Thomas
Greetings all, I'm sort of new to IP and brand new on this mailing list. J Here's my situation: I need to build a report of everything missing from our institution's library that isn't accounted for (i.e. we want to find what's been stolen/lost, etc.) That means the librarians will scan