While poking around inside the Fossil DB, I came away with several questions:

1. What is event.euser?  This column seems completely unused on my largest 
repository.  (select distinct count(euser) from event == 0)  I’ve tried 
grepping the source, and all I saw is a bunch of coalesce(user,euser) stuff, 
which I assume means it uses whichever one is set.  (I did not look at every 
last instance, however.)  So why do we need both?

2. ticketchng.username.  Also unused here.  What is this for, and why do we 
have it in addition to ticketchng.login, which does have the expected data 
here?  Grepping the code, it looks like part of the code uses “username” and 
part uses “login.”  What’s going on here?

3. Is user.photo a half-implemented feature?  All I see in the code are bits to 
copy the BLOB from one place to another, with no way to set it or display it.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to