[sqlalchemy] Re: Weird problem in SqlSoup

[bbull]

The latest trunk seems to have fixed this issue.

Thanks

On Jul 12, 6:22 pm, jason kirtland [EMAIL PROTECTED] wrote:
 bbull wrote:
  I have some code that returns what I'm calling a table object.

  return getattr(self.dbc, tablename)

  where self.dbc is an SqlSoup object and tablename is the name of the
  table.

  [..]
  TypeError: type() argument 1 must be string, not unicode

  For some reason, the line mapname = 'Mapped' +
  _selectable_name(selectable) in sqlsoup.py creates a unicode object
  instead of a string object when 'entity' is passed in.  If I put a
  simple str() around the code (mapname = str('Mapped' +
  _selectable_name(selectable))), it works with no problem.

  Any reason why only this one particular case would cause this problem?

 Try that again with the latest from trunk.

 -j


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
sqlalchemy group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en
-~--~~~~--~~--~--~---

[sqlalchemy] Re: Autoload problem with my MySql server

[bbull]

I just tested this on MySQL 4.0.20c and it seems to have solved the
autoload problem.

What is the timeframe for cutting the 0.3.9 release?

Brian

On Jul 12, 1:00 pm, jason kirtland [EMAIL PROTECTED] wrote:
 I've made changes in the trunk for 0.3.9 that I hope will take care
 of reflection issues reported in MySQL 3.23, 4.0 and 4.1, as well
 as odds and ends in current releases.  It would be super super
 useful if anyone who has had reflection issues in the past to pull
 a copy of the trunk and give it a try before we cut a 0.3.9 release.

 Some of these issues are corner cases tied to a particular point
 version of the MySQL server and/or MySQL-python.  I've tested the
 latest on around 150 different combinations, but full coverage
 would be something like 3,500 combos.  So, a little help is greatly
 appreciated!  :)  Plus, real schema are bound to be more
 challenging than my test cases.

 Cheers,
 Jason


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
sqlalchemy group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en
-~--~~~~--~~--~--~---

[sqlalchemy] Re: Autoload problem with my MySql server

[bbull]

I've run into this problem as well when working with MySQL 4.0.20c.  I
believe the code needs to read:

decode_from = connection.execute(show variables like
'character_set').fetchone()[0]

When issuing that sql at the command prompt, i get back the following:

mysql show variables like character_set;
+---++
| Variable_name | Value  |
+---++
| character_set | latin1 |
+---++
1 row in set (0.01 sec)


On Jul 3, 9:48 am, Michael Bayer [EMAIL PROTECTED] wrote:
   its this code

 decode_from = connection.execute(show variables like
 'character_set_results').fetchone()[1]

 this bug is because you have a very old version of MySQL..if you can
 figure out what the above code needs for your mysql we can patch it.


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
sqlalchemy group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en
-~--~~~~--~~--~--~---