The collection database uses SQLITE, so if you need to list or modify its content, you can make queries directly to the database using SQL. We deliberately chose not to allow adding metadata to keep the SDK and Collection implementation as simple and as efficient as possible. If your application requires metadata, I would advise you to create a database of your own choosing and then store the additional metadata there. Every time you enroll a template you receive a UUID for that template, you can then store the metadata in your database along with that UUID, this create a link between your database and the trueface database where the metadata resides.
1 Comment
N
Nezare Chafni
said
about 2 years ago
Answer
The collection database uses SQLITE, so if you need to list or modify its content, you can make queries directly to the database using SQL. We deliberately chose not to allow adding metadata to keep the SDK and Collection implementation as simple and as efficient as possible. If your application requires metadata, I would advise you to create a database of your own choosing and then store the additional metadata there. Every time you enroll a template you receive a UUID for that template, you can then store the metadata in your database along with that UUID, this create a link between your database and the trueface database where the metadata resides.
Sean S
would be a useful addition to a function like:
https://reference.trueface.ai/cpp/dev/latest/usage/identification.html?highlight=enrolltemplate#_CPPv4N8Trueface3SDK14enrollTemplateERK9FaceprintRKNSt6stringERNSt6stringE
The collection database uses SQLITE, so if you need to list or modify its content, you can make queries directly to the database using SQL. We deliberately chose not to allow adding metadata to keep the SDK and Collection implementation as simple and as efficient as possible. If your application requires metadata, I would advise you to create a database of your own choosing and then store the additional metadata there. Every time you enroll a template you receive a UUID for that template, you can then store the metadata in your database along with that UUID, this create a link between your database and the trueface database where the metadata resides.
Nezare Chafni
The collection database uses SQLITE, so if you need to list or modify its content, you can make queries directly to the database using SQL. We deliberately chose not to allow adding metadata to keep the SDK and Collection implementation as simple and as efficient as possible. If your application requires metadata, I would advise you to create a database of your own choosing and then store the additional metadata there. Every time you enroll a template you receive a UUID for that template, you can then store the metadata in your database along with that UUID, this create a link between your database and the trueface database where the metadata resides.
-
Do you support running on ARM?
-
Difference Between Lite and Full models? And do you have a Windows SDK?
-
How to get your sample apps
-
System requirements
-
Latest VisionBox image
-
Face recognition implementation
-
FR with mask and other accessories
-
Face recognition in different conditions
-
Mask detection working scenarios
-
Age detection & FRBox
See all 27 topics