[LONG WINDED INTRO]
I'm working on my own little database that pulls info from my journal files. I'm working on building the relevant SQLite tables to store my info, and I came upon a simple naming convention conflict that I've managed to blow up to an organizational existential crisis. I haven't gotten very far into setting up my database tables, but I've already noticed the json field "MarketID" pops up several times. For clarity I try to match table column names to the json fileds, so have been using "MarketID" as the cloumn name for this field. But I've also been using the naming convention of adding 'ID' to the table's name as the PRIMARY KEY, so when I started working on the Market event I found myself in a situation where "MarketID" would be used for 2 different columns. I thought about instituting a change in naming convention, but then had the idea of using the json MarketID data as the PRIMARY KEY, elegantly solving the naming conflict and possibly tying the data together in a functionally meaningful way. But when I compared the Outfitting file to the Market file from the same station (my carrier) I noticed that the MarketID is the same.
[ACTUAL QUESTION]
So, is MarketID analogous to a StationID, FacilityID, or CarrierID? It seems likely, but I just want to make sure I understand it before I start integrating it into my organization scheme. Would it be appropriate to utilize it as a StationID? Is there any chance its value could be non-unique or perhaps be used in multiple instances of the same event type leading to a situation where data is gtetting rewritten?
Also, is there maybe better documentation for the contents of the journal files? The Elite Dangerous Jouranl documentation website has been helpful, but some fields aren't always clear, and I've noticed significant differences between what's provided on the website and what's in my actual journal files.
I'm working on my own little database that pulls info from my journal files. I'm working on building the relevant SQLite tables to store my info, and I came upon a simple naming convention conflict that I've managed to blow up to an organizational existential crisis. I haven't gotten very far into setting up my database tables, but I've already noticed the json field "MarketID" pops up several times. For clarity I try to match table column names to the json fileds, so have been using "MarketID" as the cloumn name for this field. But I've also been using the naming convention of adding 'ID' to the table's name as the PRIMARY KEY, so when I started working on the Market event I found myself in a situation where "MarketID" would be used for 2 different columns. I thought about instituting a change in naming convention, but then had the idea of using the json MarketID data as the PRIMARY KEY, elegantly solving the naming conflict and possibly tying the data together in a functionally meaningful way. But when I compared the Outfitting file to the Market file from the same station (my carrier) I noticed that the MarketID is the same.
[ACTUAL QUESTION]
So, is MarketID analogous to a StationID, FacilityID, or CarrierID? It seems likely, but I just want to make sure I understand it before I start integrating it into my organization scheme. Would it be appropriate to utilize it as a StationID? Is there any chance its value could be non-unique or perhaps be used in multiple instances of the same event type leading to a situation where data is gtetting rewritten?
Also, is there maybe better documentation for the contents of the journal files? The Elite Dangerous Jouranl documentation website has been helpful, but some fields aren't always clear, and I've noticed significant differences between what's provided on the website and what's in my actual journal files.
Last edited: