BE meeting 13.05

Goal: Align with each other updates for current tickets

Participants: Tanja, Leon, Nicolas, Ahsan

Content:

Nicolas: CSV parser is done, but some questions are still open. What does CSV parser need to deliver to the YAML parser (having the data as an argument) and what to send to the database (the resulting String or SQL query). Which columns do we need for the YAML parser? String as a key and Object as a parameter.

Leon: The YAML parser is not yet started, it will be started today in the afternoon. Proposal: function iterator, do it lazily to reduce some storage. For the database, Leon proposed: for the CSV parser to have a function ReadHeader and GetNextLine function (gets a next row) and then this is a dictionary with header names as values.

Ahsan: Ahsan's opinion: better not to consume data as each row, but dump all data at once. For the database, he wants to have a list of objects where each object contains each row (to have a custom class for each CSV).

Keep in mind:

• The Async call for GetData is obsolete, this is an old option from a not simplified version.
• CSV file -> string[] -> dictionary -> SQL query.
• Assumptions: db lost connection is not that common, processing of huge data is preferred over speed of delivering data.
• Pair programming is preferred, let's try to push more pair programming.
• We don't want to have separate db for each CSV file
• Decision to merge all branches in the evening of 13. May
• Update Emil about updating all docker files in the main docker-compose (because Ahsan will create a db docker file presumably in the next Sprint and the database will be accessible after that)