drizzle docs are whacked out

Issue #2385 resolved
Mike Bayer repo owner created an issue

looks like "mysql" was badly search and replaced, also there's an ancient note about the use_unicode thing which shows a non-drizzle URL. this doc should mention that Drizzle is a mysql variant and then anything that is common with the MySQL doc should be trimmed out.

Comments (9)

  1. Former user Account Deleted

    (original author: diana) I'm trying to get the tests to pass with: ./sqla_nose.py --dburi=drizzle

    The attached patch (drizzle_tests.patch) only moves the bar a bit.

    Before: FAILED (SKIP=107, errors=72, failures=16)

    After: FAILED (SKIP=114, errors=46, failures=8)

    I need to figure out how to get the unit testing setup/teardown/etc methods working before I can go much further on this.

    (OperationalError) (1744, 'Transactional DDL not supported')
    

    Any hints would be much appreciated. Thanks!

  2. Mike Bayer reporter

    im not extremely concerned about the unit tests passing, I wonder how drizzle would even make the decision that we're doing transactional DDL ? calling commit ? what makes it say that ?

    the ticket here only referred to the documentation sections not being written correctly in drizzle/base.py and elsewhere.

  3. Former user Account Deleted

    (original author: diana) Replying to zzzeek:

    the ticket here only referred to the documentation sections not being written correctly in drizzle/base.py and elsewhere.

    Okie dokie, thx. I did start with just the docs, but in the process I was trying to write tests to suss out which parts of the existing docs were fact vs. fallacy aside from the obvious (drizzle-python vs. mysql-python, etc).

  4. Former user Account Deleted

    (original author: diana) The attached patch mostly just deletes the drizzle documentation and points the user at the mysql documentation.

    I also did a pep8/unused imports pass of the drizzle dir, and removed SET from drizzle's {{{all}}} in {{{init.py}}} since drizzle doesn't support SET.

  5. Log in to comment