On Jun 7, 10:09 am, "Joe" <[EMAIL PROTECTED]> wrote:
>
> And, yes, printing the error message returns absolutely nothing. The tuple
> following InterfaceError is both the error code and message. Unfortunately,
> it will only give me (0, '') which isn't much help.
>
I'm on Google groups and can't
On 6/7/07, Joe <[EMAIL PROTECTED]> wrote:
> > Huh the only thing I can find on InterfaceError is "Errors related to
> > the database interface and not the database itself." You might be able
> > to get some info from connection.info() . . .
>
> Yeah, I wish there was more documentation about this t
> Huh the only thing I can find on InterfaceError is "Errors related to
> the database interface and not the database itself." You might be able
> to get some info from connection.info() . . .
Yeah, I wish there was more documentation about this type of error. The
only thing info() tells me is th
> Try passing the cursor and not the connection -
Unfortunately this provided the same InterfaceError. It was one of the
first options we had tried in correcting the situation. Is there any way to
check on the status of a database connection (like an isOpen() method)? It
appeared as though the
On 6/5/07, Joe <[EMAIL PROTECTED]> wrote:
>
>
>
>
> >File "build/bdist.linux-i686/egg/MySQLdb/cursors.py", line
> 147, in execute
>
> >charset = db.character_set_name()
>
> >
>
> >InterfaceError: (0, '')
>
>
>
> We got it working. It was caused by passing a database connection to a
> module:
>
>File "build/bdist.linux-i686/egg/MySQLdb/cursors.py", line 147, in execute
>charset = db.character_set_name()
>
>InterfaceError: (0, '')
We got it working. It was caused by passing a database connection to a
module:
import MySQLdb
import module_name
connection = MySQLdb.connect(
Sorry, forgot some valuable information. If you couldn't tell from the
traceback, the error will be thrown during the first executed query that the
program runs into (no matter what that query is).
Jough
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Joe
Sent: Mo
