Bug #31771 | Cannot conect MySQL in ASP.Net | ||
---|---|---|---|
Submitted: | 23 Oct 2007 2:21 | Modified: | 21 Feb 2013 20:58 |
Reporter: | Lenh Ho Xung | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | Connector / NET | Severity: | S1 (Critical) |
Version: | 5.1.3 | OS: | Windows (SP2) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[23 Oct 2007 2:21]
Lenh Ho Xung
[26 Oct 2007 20:50]
Rick Wright
I was having this particular issue. I am able to connect using the connector. I have documented the steps I took on http://www.makingyournetwork.com/portal/CIS/tabid/54/forumid/2/scope/threads/Default.aspx It is a rather long post, so print it out. The Connector is still a little bit goofy but at least I can see the tables. One note, use a fully qualified table.fieldname in your query specifier. You cannot accept the default {specify columns from a table or view} setting because it places [ ] (square brackets) around the field names and MySQL Server is not happy about their presence. I cannot get the advanced SQL generation options to work. The update, delete and insert settings are grayed out. Buty you can build your own when you choose option 1). Specify a custom SQL statement or stored procedure.
[3 Sep 2008 14:57]
Tonci Grgin
Seemingly this slipped by me so I apologize. Lenh, does this represent problem for you still? Even with new c/NET? Rick, the link is dead. Can you please make text available to others?
[3 Oct 2008 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[26 May 2011 15:16]
Julio Casal
Please let us know if this issue is still happening with Connector/Net 6.1+ and if so please provide reproduction steps and a sample project that will show the error.
[26 Jun 2011 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[13 Jan 2012 21:27]
ninijeaddylen ninijeaddylen
propecia or proscar propecia prostate cancer <a href=http://buypropeciaonline371.posterous.com>buy propecia online</a> propecia women side effects propecia reviews