issues: 737855731

This data as json

id node_id number title user state locked assignee milestone comments created_at updated_at closed_at author_association pull_request body repo type active_lock_reason performed_via_github_app reactions draft state_reason
737855731 MDU6SXNzdWU3Mzc4NTU3MzE= 199 @db.register_function(..., replace=False) to avoid double-registering custom functions 9599 closed 0     1 2020-11-06T15:39:21Z 2020-11-06T18:30:44Z 2020-11-06T18:30:44Z OWNER  

I'd like a mechanism to optionally avoid registering a custom function if it has already been registered.

SQLite doesn't seem to offer a way to introspect registered custom functions so I'll need to track what has already been registered in sqlite-utils instead.

Should I register the custom rank_bm25 SQLite function for every connection, or should I register it against the connection just the first time the user attempts an FTS4 search? I think I'd rather register it only if it is needed.

Originally posted by @simonw in https://github.com/simonw/sqlite-utils/issues/198#issuecomment-723145383

 140912432 issue     
{
    "url": "https://api.github.com/repos/simonw/sqlite-utils/issues/199/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed

Links from other tables