[LARP DB] Welp, ran into one issue that appears it's going to be a minor issue for the front end programmer, but relatively minor. Basically there's going to be a wrapper JSON object called "rootElement" that needs to be removed entirely. The body of a POST or PUT must not contain it.
It's an artifact of the data schema I'm using, but yeah we'll talk. I don't see it as a big deal, but I can't remove it at my end as it gets tacked on with the GET response.
ooph, well, hope all goes well! And yeah, it's really just an extra key that gets tacked in when returning a Microsoft JsonDocument class that wraps the outgoing JSON. It appears to be automatically added when the response to the GET happens.
I think the big game changer is my implementation of JSONb in postgres, which means we can store item cards in the same table, no matter if it's a sword, or a Gundam or a Pokemon.
Since the front end would have to know the difference between the types or items anyways and then account for those differences anyways, the overall effect is the same while remaining elegant in backend design.
We might still have some work for the auth functionality as well, but that shouldn't be difficult. Can I see your schema? I might still have use for my and Dave's stuff for a Mobile app of some sort.
I have a current schema, but it might change in the future. I'm working with Jantra on that since they'll be working the front end effort and we need to agree on the overall setup.
I'll send it along when I'm done with work. I'm on my work laptop currently.
I hate to be the one to bring this up but there is also a contingent from Otakon LARP that’s been working on something like this, so you may want to inform them as well just so there’s not too much duplication of effort going on
Well I haven't heard anything from anyone in Otakon in a long long time. And at this point I'm sure I can get this thing running in basic mode by the end of May.
Like at this point we've been complaining we need this for YEARS. Forgive me if I feel a little bit uncaring if I run a monster truck over work someone else was doing but never shared.
I think we can get by with a bargain basement host setup, (single box +web hosting) since it's going to have maybe a few users hitting it at once. The cost would be comparable to dropbox. I'm willing to front the costs for a year if everyone helps with data entry.
Nah, not really. I was just wondering if you'd thought about it, since it's a bit more resource intensive than Python on the backend. I will offer the use of the www domain for accessing it.
I mean, if you know C# you'll probably know the Java I'm writing. I just don't want to learn the basics of C# to get the project going, since that'd throw off my interest.
worse comes to worst we just go with divying up data entry. We'd likely have enough people with access to the DB that each person would only need to do about 30-50 sheets.
For an initial import, I'd think having them put into a spreadsheet might be better, if only because it wouldn't involve waiting to post and get responses back, and it could all be done in bulk
::shrug:: it's 6 of one, half dozen of the other, far as I'm concerned. The work needed to get everything formatted in a spreadsheet would be the same as cutting and pasting into a web form, from my perspective. DB posting speed is largely insignificant with the work that needs to be done for data entry.
But instead it's "Fields":{"rootElement":{<JSON stuff here>}}
{
"seriesguid": "d230601a-8cc8-11ea-8e54-c386fdbf80e6",
"name": "Nene's Hardsuit",
"typeGuid": "894caf3e-8d4f-11ea-99fe-5ff858a827e9",
"fields":
{"Resilence":"1", "Grade":"0", "Jump":"+1",
"INTEGRITY":"15","HS":"-5", "Energy":"25"}
}
{ "seriesguid": "d230601a-8cc8-11ea-8e54-c386fdbf80e6",
"name": "Nene's Hardsuit",
"typeGuid": "894caf3e-8d4f-11ea-99fe-5ff858a827e9",
"fields": {
"rootElement": { "HS": "-5", "Jump": "+1", "Grade": "0", "Energy": "25", "INTEGRITY": "15", "Resilence": "1"}
}
I'll send it along when I'm done with work. I'm on my work laptop currently.