Steve Ramacher a utilisé son clavier pour écrire :
>> Nothing I want said fbmembership provider.cs. i have correct some bug :
>> 1) when you create an user IsOnline is not set so a exception is raised
>
>> because the domain's bool is NOT NULL.
>
Hello in the cvs i have put your changes but i have
>Nothing I want said fbmembership provider.cs. i have correct some bug :
>1) when you create an user IsOnline is not set so a exception is raised
>because the domain's bool is NOT NULL.
I have a script that was corrected and forwarded to Le roy Arnaud about
3 weeks ago that correct these concerns
Le roy Arnaud wrote:
> Nothing i want said fbmembership provider.cs. i have correct some bug :
:P
--
Jiri {x2} Cincura
http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com
-
Using Tomcat but need to do more? Need to su
> Well, with 8k page size, the table roles is OK... But I think the 4k page
> size we should handle as base. But changing the implementation isn't good.
> Maybe we should way, if somebody will report this as a problem and then make
> final decision. OK?
>
Ok.
> What's wrong with membership pro
Le roy Arnaud wrote:
> I have look to add primary key on each table but there is a problem
> with the role and usersrole tables because this table have not column
> that accept primary key because their size is too big so i must change
> the struct of these tables and change the role provider !
>> yes, in fact they must be an index on each provider's table
>
> OK, nice. Will you commit new sql script?
>
I have look to add primary key on each table but there is a problem
with the role and usersrole tables because this table have not column
that accept primary key because their size is to
Jiri Cincura a couché sur son écran :
> Le roy Arnaud wrote:
>> it could be a good idea but for exemple in the membership provider
>> delete function have a parameter ("deleteAllRelatedData") that define
>> if all related data of the users should be delete and if we put an fk
>> the related dat
Le roy Arnaud wrote:
> it could be a good idea but for exemple in the membership provider
> delete function have a parameter ("deleteAllRelatedData") that define
> if all related data of the users should be delete and if we put an fk
> the related data will be always delete.
:\
> An other pro
> OK, nice. Will you commit new sql script?
Ok i will commit this changes tomorrow
> BTW what about adding (optional) FK constraint to be able to delete users
> from console without havving any stub in database. What do you think?
it could be a good idea but for exemple in the membership provide
Le roy Arnaud wrote:
> Jiri Cincura a émis l'idée suivante :
>> Just small note, what about adding PK into RoleProvider's table? With a lot
>> of users/roles this can be a bottleneck without index.
>
> yes, in fact they must be an index on each provider's table
OK, nice. Will you commit new sql
Jiri Cincura a émis l'idée suivante :
> Just small note, what about adding PK into RoleProvider's table? With a lot
> of users/roles this can be a bottleneck without index.
yes, in fact they must be an index on each provider's table
-
Just small note, what about adding PK into RoleProvider's table? With a lot
of users/roles this can be a bottleneck without index.
--
Jiri {x2} Cincura
http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com
-
Using Tomc
12 matches
Mail list logo