Open maxbates opened 10 years ago
We already deal with this for create, but you are correct, we need to also add it for delete.
On Fri, May 16, 2014 at 7:58 PM, Maxwell Bates notifications@github.comwrote:
Because autocomplete is created on build rather than querying the database directly as needed, it needs to monitor changes to new + existing objects.
For example, when an object is destroyed, it will still appear in the autocomplete.
— Reply to this email directly or view it on GitHubhttps://github.com/CIDARLAB/clotho3/issues/294 .
J. Christopher Anderson, Ph.D. Assistant Professor Department of Bioengineering http://andersonlab.qb3.berkeley.edu/
Office: 512E Energy Biosciences Building (EBB) Lab: 5th Floor EBB
Mailing Address: J. Christopher Anderson University of California, Berkeley 512E Energy Biosciences Building Berkeley, CA 94720
and set() presumably
yeah, the name could change in set
On Fri, May 16, 2014 at 8:14 PM, Maxwell Bates notifications@github.comwrote:
and set() presumably
— Reply to this email directly or view it on GitHubhttps://github.com/CIDARLAB/clotho3/issues/294#issuecomment-43396187 .
J. Christopher Anderson, Ph.D. Assistant Professor Department of Bioengineering http://andersonlab.qb3.berkeley.edu/
Office: 512E Energy Biosciences Building (EBB) Lab: 5th Floor EBB
Mailing Address: J. Christopher Anderson University of California, Berkeley 512E Energy Biosciences Building Berkeley, CA 94720
Because autocomplete is created on build rather than querying the database directly as needed, it needs to monitor changes to new + existing objects.
For example, when an object is destroyed, it will still appear in the autocomplete.