ENH: Implement queries and entity retrieval

Summary

See https://gitlab.indiscale.com/caosdb/customers/lfpb/management/-/issues/386.

Focus

Point the reviewer to the core of the code change. Where should they start
reading? What should they focus on (e.g. security, performance,
maintainability, user-friendliness, compliance with the specs, finding more
corner cases, concrete questions)?

Test Environment

How to set up a test environment for manual testing?

Check List for the Author

Please, prepare your MR for a review. Be sure to write a summary and a focus and create gitlab comments for the reviewer. They should guide the reviewer through the changes, explain your changes and also point out open questions. For further good practices have a look at our review guidelines

• All automated tests pass
• Reference related Issues
• Up-to-date CHANGELOG.md
• Annotations in code (Gitlab comments)
  • Intent of new code
  • Problems with old code
  • Why this implementation?

Check List for the Reviewer

• I understand the intent of this MR
• All automated tests pass
• Up-to-date CHANGELOG.md
• The test environment setup works and the intended behavior is reproducible in the test environment
• In-code documentation and comments are up-to-date.
• Check: Are there spezifications? Are they satisfied?

For further good practices have a look at our review guidelines.

mentioned in merge request caosdb-juliainttest!3 (merged)

marked the checklist item Reference related Issues as completed

added 8 commits

• d7537e93 - MAINT: Add caosdb_client.json for tests
• c01a8864 - DOC: Add hint to config file
• 1cf223b6 - DRAFT: Move Transaction module to separate file
• 82d75b25 - DRAFT: Begin tests for transactions
• 3daa6ee5 - ENH: Implement create_transaction
• e40a8c77 - MAINT: Add caosdb config file
• 381fff84 - ENH: Implement retrievals and update docstrings
• a1ce9bdd - STY: whitespaces

Compare with previous version

Unfortunately, Documenter.jl doesn't support the Private argument in @index so we have to join everything into one index. I still like having one now that we have so many elements in our API documentation, though.

This is kind of neat; Julia automatically converts anything that looks like a Vector{String} to a C-array of char pointers.

changed this line in version 4 of the diff

added 1 commit

• 4773e5ac - DRAFT: Pipeline

Compare with previous version

added 6 commits

• 45dabd84 - DRAFT: Begin implementation of entities
• 5ef97a84 - ENH: Add Exception type for client exceptions
• 475a378f - FIX: Correct arguments for retrieve_by_ids
• 2b379aff - DRAFT: Begin implementation of entities
• f5bd5529 - ENH: Add test for entities
• 0be053a7 - DRAFT: Add a lot of setters, getters, and helper functions

Compare with previous version

added 2 commits

• 379a133b - ENH: Add convenience wrappers for Integer indices
• 20939d95 - ENH: Add size checking to getters

Compare with previous version

added 1 commit

• b3e4ab79 - MAINT: Move remaining modules to separate files

Compare with previous version

added 1 commit

• bdcaceb1 - ENH: Finish retrieve and query transactions

Compare with previous version

added 1 commit

• 1e651982 - DOC: Add hint on COUNT queries

Compare with previous version

Nothing changed, just moved to separate file.

Moved the remaining modules to separate files since CaosDB.jl became quite crowded.

The _deletable flag isn't actually needed on the Julia side, but we still have it in order to prevent any strange memory problems if the structs in Julia didn't exactly match the C structs.

Set it to false in the constructor to reflect the default value in the C structs.

Mostly just moved ...

This one is new. It's meant for CaosDB specific errors on the Julia side.

Get the correct error code for errors in the higher-order client.

Nothing new, just moved.

This is never created on its own, only as a part of a transaction. That's why we don't add a destructor (i.e., finalizer) here (there aren't even create_result_set and delete_result_set functions in ccaosdb).