hm...sqlite not available?  we need to join datasets from two physically
separate dbs and this seemed like the most lightweight option.  also,
there's no requirement that this run on a provisioned server, it can run
anywhere from which the two source databases can be reached.


On Fri, Mar 21, 2014 at 10:32 AM, e0d <notifications@github.com> wrote:

> In forums/clean_cs_users.py:
>
> > +FETCHMANY_SIZE=10000
> > +
> > +logging.basicConfig(level=logging.INFO, format='%(asctime)s %(levelname)s: %(message)s')
> > +logger = logging.getLogger('')
> > +
> > +JoinedUser = namedtuple('JoinedUser', 'cs_id cs_username cs_email cs_read_count lms_id lms_username lms_email')
> > +
> > +def _drop_sqlite_table(sqlite_cx, name):
> > +    """
> > +    """
> > +    try:
> > +        sqlite_cx.execute("DROP TABLE {}".format(name))
> > +    except sqlite3.OperationalError:
> > +        pass
> > +
> > +def load_lms_users(mysql_cx, sqlite_cx):
>
> Using a DB here seems like overkill to me and introduces a requirement for
> running the script that isn't typically available on our servers.
>
> --
> Reply to this email directly or view it on GitHub<https://github.com/edx/edx-tools/pull/5/files#r10837453>
> .
>