Frankly, I don't know what is the UCLA MySQL database server. If it means biodb2.bioinformatics.ucla.edu, MySQL server is not running on that.
I think you are right. No UCLA pygr.Data resources are linked with MySQL database. Namshin Kim On Fri, Oct 24, 2008 at 1:19 AM, Christopher Lee <[EMAIL PROTECTED]> wrote: > > I don't think we even have a publicly accessible MySQL server, so I > don't know what you're referring to. Could you identify the specific > pygr.Data resource name that you're having this problem with, and > exactly how you request it? > > Namshin, am I right in thinking no UCLA external pygr.Data resources > should reference a UCLA external MySQL database server? > > -- Chris > > > On Oct 23, 2008, at 12:25 AM, Jenny Qing Qian wrote: > > > um... > > > > What's the version of the mysql server on your end? The version of > > mysql client installed on my computer is 5.0.51. The 'MySQL > > connection' bug has been reported to occur when a 5.0.51 client or > > lower tries to talk to a 5.0.52 server. > > > > Also, does the computer hosting the UCLA server have a 64-bit > > processor? My laptop only has a 32-bit processor. 'A 32-bit > > processor talks to a 64-bit processor' could also be the cause of > > the problem. > > > > jenny > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
