database connection

2023-09-16T13:48:47.370000Z

UCanAccess exhibits a cleaning behavior where it doesn't raise an error when a column name in a SQL query is ambiguous, unlike many other database engines that do. Instead, UCanAccess appears to prioritize the first table in the FROM clause that contains the column with the same name. This differs from the behavior of databases like Access, SQL Server, MySQL, DB2, and Oracle, which explicitly flag such situations as errors.

Is there a configuration option or a way to modify UCanAccess to align with the standard behavior of raising an error for ambiguous column names in queries?

database connection

2018-11-25T15:16:11.950000Z

I have python 3.7 version which version it will support of mysql

Mysql-Python 1.2.3 vs Mysql-Python 1.2.4

2018-05-15T15:58:45.193000Z

We were using Mysql-Python 1.2.3 binaries (Sourceforge) and planning to update to Mysql-Python 1.2.4 binaries from Sourceforge. We found below 5 packages are missing in 1.2.4 version compared to 1.2.3. Are there any relevant ones for the same in 1.2.4 ?

backports
chardet
iotop
requests
urllib3

Thanks,
-Umesh

Using a python variable in a sql statement

2018-02-09T18:19:18.135000Z

Thanks so much. Solved my problem.

Error 2006 ('Mysql has gone away')

2017-07-17T07:17:44.205000Z

This is my code

import config
import MySQLdb
import sys
from collections import OrderedDict

class DatabaseConnect(object):
    _db_connection = None
    _db_cur = None
    # __session = None
    # __connection = None

    def __init__(self):
        self._db_connection = MySQLdb.connect(
            host=config.mysqlhost,
            user=config.mysqluser,
            passwd=config.mysqlpass,
            db=config.mysqldbnm
        )
        # self._db_connection.ping(True)
        self._db_cur = self._db_connection.cursor()

    def __del__(self):
        self._db_connection.close()

    def query(self, query, param=None):
        return self._db_cur.execute(query, param)

    def select(self, table, where=None, *args, **kwargs):
        result = None
        query = 'SELECT '
        keys = args
        values = tuple(kwargs.values())
        l = len(keys) - 1

        if keys:
            for i, key in enumerate(keys):
                query += "`" + key + "`"
                if i < l:
                    query += ","
        else:
            query += '*'

        query += 'FROM %s' % table

        if where:
            query += " WHERE %s" % where
        # End if where

        # self.__open()
        self._db_cur.execute(query, values)
        number_rows = self._db_cur.rowcount
        number_columns = len(self._db_cur.description)

        if number_rows >= 1 and number_columns > 1:
            result = [item for item in self._db_cur.fetchall()]
        else:
            result = [item[0] for item in self._db_cur.fetchall()]
        # self.__close()

        return result

    def update(self, table, where=None, *args, **kwargs):
        query = "UPDATE %s SET " % table
        keys = kwargs.keys()
        values = tuple(kwargs.values()) + tuple(args)
        l = len(keys) - 1
        for i, key in enumerate(keys):
            query += "`" + key + "` = %s"
            if i < l:
                query += ","
            # End if i less than 1
        # End for keys
        query += " WHERE %s" % where

        # self.__open()
        self._db_cur.execute(query, values)
        self._db_connection.commit()

        # Obtain rows affected
        update_rows = self._db_cur.rowcount
        # self.__close()

        return update_rows

    def insert(self, table, *args, **kwargs):
        values = None
        query = "INSERT INTO %s " % table
        if kwargs:
            keys = kwargs.keys()
            values = tuple(kwargs.values())
            query += "(" + ",".join(["`%s`"] * len(keys)) % tuple(keys) + \
                ") VALUES (" + ",".join(["%s"] * len(values)) + ")"
        elif args:
            values = args
            query += " VALUES(" + ",".join(["%s"] * len(values)) + ")"

        # self.__open()
        self._db_cur.execute(query, values)
        self._db_connection.commit()
        # self.__close()
        return self._db_cur.lastrowid

    def delete(self, table, where=None, *args):
        query = "DELETE FROM %s" % table
        if where:
            query += ' WHERE %s' % where

        values = tuple(args)

        # self.__open()
        self._db_cur.execute(query, values)
        self._db_connection.commit()

        # Obtain rows affected
        delete_rows = self._db_cur.rowcount
        # self.__close()

        return delete_rows

    def select_advanced(self, sql, *args):
        od = OrderedDict(args)
        query = sql
        values = tuple(od.values())
        # self.__open()
        self._db_cur.execute(query, values)
        number_rows = self._db_cur.rowcount
        number_columns = len(self._db_cur.description)

        if number_rows >= 1 and number_columns > 1:
            result = [item for item in self._db_cur.fetchall()]
        else:
            result = [item[0] for item in self._db_cur.fetchall()]

        # self.__close()
        return result

wrong architecture error

2012-11-16T15:43:25.936000Z

I'm pretty sure he's not using homebrew or MacPorts. I'm not sure what the "right way" to solve this problem is, but, could you post the output of running mysql_config?

wrong architecture error

2012-11-16T14:54:36.698000Z

I did this: 1. uninstall MySQL and mysql-python 2. reinstall MySQL 64-bit 3. reinstall mysql-python (at this point, the django syncdb command was failing due to a missing library, libmysqlclient.18.dylib) 4. added environment variable DYLD_LIBRARY_PATH=/usr/local/mysql...../lib, to point to the directory containing the missing dylib With those changes, the django syncdb command is now working correctly with a mysql database. Thanks for your help.

wrong architecture error

2012-11-16T03:31:10.116000Z

I knew there had to be a fat binary in there somewhere... So you are linked against an i386 MySQL library. I think if you get the 64-bit MySQL build, your problem will go away.

wrong architecture error

2012-11-16T02:44:28.983000Z

The MySQL installer I used is: mysql-5.5.28-osx10.6-x86.dmg python supports both architectures, and the other two are i386. I also tried running Python with "arch -i386 python", but it made no difference file `which python` /usr/bin/python: Mach-O universal binary with 2 architectures /usr/bin/python (for architecture i386): Mach-O executable i386 /usr/bin/python (for architecture x86_64): Mach-O 64-bit executable x86_64 ip96-62:mysite groverf$ file `which mysql` /Users/groverf/bin/mysql: POSIX shell script text executable ip96-62:mysite groverf$ file /usr/local/mysql/bin/mysql /usr/local/mysql/bin/mysql: Mach-O executable i386 ip96-62:mysite groverf$ file /Library/Python/2.7/site-packages/_mysql.so /Library/Python/2.7/site-packages/_mysql.so: Mach-O bundle i386 ip96-62:mysite groverf$

wrong architecture error

2012-11-16T01:39:39.785000Z

Well, it's definitely odd. Can you try creating a virtualenv environment and installing MySQLdb in there? Are you sure your MySQL installation is correct? If you downloaded from http://www.mysql.com/downloads/mysql/#downloads specifically which one? You need to make sure the architecture of Python and MySQL match. Probably the best way to test this is with the following commands: $ file `which python` $ file `which mysql` # or mysql_config $ file /Library/Python/2.7/site-packages/_mysql.so They should either all be x86-64 or i386 but not a mix.

Recent posts to Discussion

database connection

database connection

Mysql-Python 1.2.3 vs Mysql-Python 1.2.4

Using a python variable in a sql statement

Error 2006 ('Mysql has gone away')

wrong architecture error

wrong architecture error

wrong architecture error

wrong architecture error

wrong architecture error