On Wed, Aug 14, 2019 at 10:55 AM, Victoria wrote:
3. upload CSV tables:
If a table in CSV format is imported into one of the databases, it happens again and again that some entries of the table are simply "forgotten" when imported, and you have to add them manually if you want them to appear in the database. A regularity for this is not recognizable.
Victoria
I can answer this one:
- The CSV file must be built with utf-8 as the option because json only accepts utf-8.
In some cases you will get an early termination of the row followed by nonsense rows if you have non-utf-8 characters in your CSV file.
In other cases you might see a little black diamond inserted to indicate each illegal character.
Note: Groups.io operates somewhat like the old, dark-ages HP 2000 Time Share system, with users allotted a specific amount of connection time.
If your table gets very large you "connection slot" may time out while uploading it and you will see a (pink banner) message indicating that you are "No longer logged in"!? ?
And you actually have been logged out.? You must wait some undefined period of time and then use the usual login procedure.
If the system is still processing your table, you will not be able to log back in.
Mark suggested that I break up my table into smaller pieces to reduce the occurrence of this issue.
My current table is about 800 KBytes in JSON format and will continue to grow
Since the ID structure doesn't allow for inserts I have to reload the table to add another row and this requires extra steps to set up a basic 0 row JSON file.? I've built that "starter file" and updating requires me to delete the entire database, upload the JSON Starter file and then upload the actual CSV file.
To make Mark happy I will have to rebuild my background AccessDatabase that is used for actual maintenance of my database and generation of the CSV file in utf-8 format so that it outputs 2 or more segments.
--
Bob Bellizzi
