Bug or future?

[darkman.cv]

//DbProfileProvider
//v. 2.51
public override ProfileInfoCollection FindProfilesByUserName(ProfileAuthenticationOption authenticationOption, string usernameToMatch, int pageIndex, int pageSize, out int totalRecords)

...
string text1 = "SELECT u.username, u.lastactivitydate, p.lastupdateddate FROM aspnet_profiles p, aspnet_users u WHERE p.userid = u.userid AND u.applicationname = :applicationname AND u.username LIKE :username ";

...
IDataReader reader1 = command1.ExecuteReader();
collection1 = new ProfileInfoCollection();
while (reader1.Read())
{
string text2 = (string) reader1.GetValue(0);
DateTime time1 = (DateTime) reader1.GetValue(1);
DateTime time2 = (DateTime) reader1.GetValue(1);
collection1.Add(new ProfileInfo(text2, false, time1, time2, -1));
}
reader1.Close();
---
DateTime time1 = (DateTime) reader1.GetValue(1);
DateTime time2 = (DateTime) reader1.GetValue(1);

Why use twice last activity date?

[Alexey]

Please specify what exactly you need or what is the problem. Where is this code snippet from?

[darkman.cv]

namespace CoreLab.PostgreSql.Web.Providers
class DbProfileProvider
function FindProfilesByUserName

[Alexey]

Yes, it is a bug. We will fix it. Look forward to the next build.

[Alexey]

New build is available for download now.