diff options
author | Arun Isaac | 2021-12-24 16:04:30 +0530 |
---|---|---|
committer | Arun Isaac | 2021-12-24 16:04:30 +0530 |
commit | d8d9d55016aa431756e97d0bd47a51f5fbf37f16 (patch) | |
tree | d691dfae74b33ee14e5b2a62dbfac9895ee2da50 | |
parent | 882b9fd2e23598d4dc8b089721839a10d6f45add (diff) | |
download | gn-transform-databases-d8d9d55016aa431756e97d0bd47a51f5fbf37f16.tar.gz |
BUGS: Add bug tracker.
* BUGS.org: New file.
-rw-r--r-- | BUGS.org | 23 |
1 files changed, 23 insertions, 0 deletions
diff --git a/BUGS.org b/BUGS.org new file mode 100644 index 0000000..ed1e9ac --- /dev/null +++ b/BUGS.org @@ -0,0 +1,23 @@ +#+TITLE: Bugs and tasks + +* TODO Construct SPARQL query results from JSON instead of CSV :minor:easy: + <2021-12-24 Fri> + sparql-query-results in visualize-schema.scm should retrieve SPARQL + query results in JSON instead of CSV. CSV ignores type information + and returns everything as a string. This results in unnecessary + conversions such as using string->number. +* TODO Specification of field alias in define-dump is a leaky abstraction :wish: + <2021-12-24 Fri> + In define-dump expressions, database fields can be referenced by + (field TABLE COLUMN ALIAS) in addition to (field TABLE + COLUMN). Specification of the field alias in the first form is a + leak in the abstraction. There is no need for the caller to know + anything about field aliases. define-dump should be able to set up + aliases transparently. +* TODO Guess string encodings :grave: + <2021-12-24 Fri> + Over the years, strings have been stored in the database using + different character encodings. That is why when they are all + interpreted in UTF-8, they appear to have unprintable + characters. Somehow, guess the encoding of the retrieved strings and + compensate. |