config file in examples doesn't return the port

Bug #598706 reported by Giuseppe Maxia
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL Connector/Python
Fix Released
Low
Geert JM Vanderkelen

Bug Description

the config.py in the examples directory doesn't return the port.
what it does now:
        return {
            'host' : cls.HOST,
            'database' : cls.DATABASE,
            'user' : cls.USER,
            'password' : cls.PASSWORD,
            'charset' : cls.CHARSET,
            'use_unicode' : cls.UNICODE,
            'get_warnings' : cls.WARNINGS,
            }

What it should do (and indeed after this change it works fine):
        return {
            'host' : cls.HOST,
            'database' : cls.DATABASE,
            'user' : cls.USER,
            'password' : cls.PASSWORD,
            'port' : cls.PORT,
            'charset' : cls.CHARSET,
            'use_unicode' : cls.UNICODE,
            'get_warnings' : cls.WARNINGS,
            }

Python version 2.6.1 - MySQL version: many - Platform Mac OSX

Related branches

Revision history for this message
Geert JM Vanderkelen (geertjmvdk) wrote :

revno: 251
committer: Geert Vanderkelen <email address hidden>
branch nick: myconnpy-dev
timestamp: Wed 2010-08-11 18:06:49 +0200
message:
  Fix: examples.config.Config.dbinfo() not returning TCP port

  o Bug lp:586003
  o Config.dbinfo() now includes the TCP port
  o Adding test case
  o Updating ChangeLog

Changed in myconnpy:
status: New → Fix Committed
importance: Undecided → Low
assignee: nobody → Geert JM Vanderkelen (geertjmvdk)
Revision history for this message
Geert JM Vanderkelen (geertjmvdk) wrote :

Went also in 0.1:

revno: 243
committer: Geert Vanderkelen <email address hidden>
branch nick: myconnpy-dev
timestamp: Wed 2010-08-11 18:33:56 +0200
message:
  Fix: examples.config.Config.dbinfo() not returning TCP port

  o Bug lp:586003
  o Config.dbinfo() now includes the TCP port
  o Adding test case
  o Updating ChangeLog

Changed in myconnpy:
milestone: none → 0.2.0
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.