Problem recognizing second user created with membership provider

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for MySQL
Post Reply
Posts: 10
Joined: Tue 20 Dec 2005 18:30

Problem recognizing second user created with membership provider

Post by kevink » Tue 25 Apr 2006 19:21

I was having a problem logging on with the second user created with the Core Lab membership provider. The first user could log on fine but not the second. I took a look at the sql being sent to my MySQL server and noticed this SQL statement from CoreLab that I think is a problem.

SELECT Password, u.UserId, Email, PasswordQuestion, PasswordAnswer, Comments, IsApproved, IsLockedOut, CreationDate, LastLoginDate, LastActivityDate, LastPasswordChangedDate, LastLockoutDate FROM aspnet_membership m, ASPNET_USERS u WHERE u.ApplicationName = '/campuses' AND u.UserName = 'Kevin'

For one thing, the aspnet_users table is capitalized in this statement and is not the InstallWebTables.sql. Since MySQL is case sensitive on non-windows machines I had to create a view for ASPNET_USERS that selects aspnet_users.

Second, the tables aspnet_membership and ASPNET_USERS are not joined together so if you run the sql statement you get multiple records returned for a single user selected.

I am using version 3.50.10.

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

Post by Alexey » Wed 26 Apr 2006 07:36

"Join" bug was fixed in the latest release version (available from our site).
Case sensitiveness will be fixed in the next version.

Post Reply