VS2005 SqlDataSource

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for MySQL
Post Reply
TillmanZ
Posts: 19
Joined: Sat 13 May 2006 04:11

VS2005 SqlDataSource

Post by TillmanZ » Sun 14 May 2006 02:48

Hi,

it seems as if the auto-generated SQL statements will not work with the MySQLConnector. VS2005 generates square-brackets [] around each field name. Obviously something mysql (running 4.0.x on Linux) doesn't like.

Is this a bug or can I fix it by using any magic?


Cheers

Alexey
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Post by Alexey » Mon 15 May 2006 07:33

You should remove all square brackets manually.

TillmanZ
Posts: 19
Joined: Sat 13 May 2006 04:11

Post by TillmanZ » Mon 15 May 2006 21:02

Thanks for your support - it does of course work to omit the square brackets but the sqldatasource then identifies the select query as "custom" and thus I will not be able to see the data structure (columns) at design time when working with grids.
Obviously it's not really a big thing to change in the corelab adapter to delete the brackets before sending the string to the mysql server.
When will that bug be fixed?

Best regards,

Tillman Zschucke

Alexey
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Post by Alexey » Tue 16 May 2006 13:44

This problem is connected with SqlDataSource component. We can't change it. We will try to workaround this problem. Look forward to the next releases.

Guest

Post by Guest » Tue 16 May 2006 22:08

When can this next release be expected?

Alexey
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Post by Alexey » Wed 17 May 2006 06:26

We don't guarantee to fix this problem in the next release. I repeat: it's VS's problem.

TillmanZ
Posts: 19
Joined: Sat 13 May 2006 04:11

Post by TillmanZ » Wed 17 May 2006 13:47

Thanks Alexey for explaining the situation.

I was hoping that the corelab connector could filter those square brackets before sending the sql query to the server.
Am I missing something in that thought?

Best regards,

Tillman

Alexey
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Post by Alexey » Thu 18 May 2006 06:39

It would hardly be a solution. It would disfigure MySQLDirect .NET infrastructure. We are looking for another way to resolve this.

Post Reply