Yet another plea for information:
Are there any resources out there that deal with writing data to multiple tables? #room#sql#kotlin
I have several tables, and need to both insert and update them with data from my UI/Domain Layer.
e.g. a new Scoundrel needs to Insert ScoundrelEntity, and maybe Insert new CrewEntity, and update CrewScoundrelCrossRef.
I need to do this for several Relationships.
I will also need to edit/delete
Is there any info on this?
Latest problem:
Special Abilities are stored as List<String>
Hand-knitted TypeConverter is splitting on comma when retrieved from database (as that is how Lists are stored)
Solutions?
convert using JSON or some other library
rewrite Converter
rebuild schema to make Abilities their own table, linked Many-to-Many (scoundrels have Many Abilities, Abilities can be had by Many Scoundrels). This is probably the better way, long term, but introduces a new layer of complexity... #room#kotlin
Whelp, I'm being dumb again, but aren't tutorials meant to assume I'm dumb?
I have my 2 Entity tables, plus a CrossRef table (Scoundrels, Contacts, ScoundrelContactCrossRef)
I can read and write the 2 main tables.
How do I write a new "Scoundrel with associated Contacts" to the 3 tables? I've got it defined in my UI/Domain, and I click SAVE, and... what do I tell ROOM/SQL? #kotlin#room#sql#code#androidDev
Am I being a bit dumb, or is making a database that has more than 1 table a Herculean Labour?
Scoundrels, Crews and Contacts.
A Scoundrel is in 1 Crew.
A Crew has 0+ Scoundrels.
Contacts are known to individual Scoundrels and/or Crews. A Contact has a Rating (Friend/Neutral/Hostile) with each Scoundrel/Crew.
I need to call each and every combination.
How complicated is this meant to be, as I seem to be making a pig's ear of the whole thing!
...and I've run into the same problem I hit before...
I have 3 Entities (Scoundrels, Crews, Contacts)
I have "Scoundrel with Crew" working (Each scoundrel is in exactly 1 Crew. A Crew can have 0+ Scoundrels)
I need to add Contacts. Each Contact can be known to many Scoundrels, and Many Crews.
Each Contact also has a Rating ("Friend", "Neutral" or "Hostile") with each relationship.
I'd like to start by building adding Scoundrels/Contacts relationships
For example as our side streets in #London are cleared of central areas (aka side roads. We have #room for #polytunnels and other street #initiatives to feed our need for food, home and #solarcooking etc.
The better world is calling us from the future feature
Hidden Chambers Found in Crumbling Pyramid 200 Years After Prediction
In 1836, Egyptologist John Shae Perring was excavating the Pyramid of Sahure (also known as Sahura) when he noticed a debris-filled passageway.
An expert on floor plans for these types of structures, he surmised there might be storage rooms beyond.
But it would take another nearly 200 years to finally confirm his suspicions. https://www.sciencealert.com/hidden-chambers-found-in-crumbling-pyramid-200-years-after-prediction#pyramid#hidden#room#Sahure#egypt
Why does #Android#Room complain that it "cannot figure out how to save this field into database" if all I did was to migrate the library from kapt to KSP?
Big Database Post: #Room#kotlin#android
I have my basic App. It allows Users to record details of Quests for #TTRPG.
It uses a single table, with mostly String fields.
I would like to expand, so that each field could hold more data.
e.g. Location ("The Swamp of Doom", "Wizard's Tower") could be it's own table, with each entry having more info.
I could write a sprawling SQL-Helper class to convert everything back and forth to the DTOs used by UI, but isn't Room meant to help?
more...
Now that you've got your head around that, let's go deeper.
For a start, any room member can add a local address for the homeserver of their account. Even if someone already has. Because #room:[my homeserver] - as in the example above - is not the only local address you can add. Oh no.
You can add any name. I can join Alice and Bob's room and add the address #rubberchicken:myserver.nz. If anyone with mod powers in the room publishes that name, it can now be used to join the room.
PSA: The Matrix URI scheme has been supported by all mainstream web engines, namely Blink, Gecko and WebKit, so instead of throwing around clownflared URLs like https://matrix.to/#/#room:server.example and https://matrix.to/#/#user:server.example, use matrix:r/room:server.example and matrix:u/user:server.example.
The migration of large communities from Reddit to Lemmy is like a world-renowned band performing an acoustic set in a library for 50 people.
The fanbase is still large, but the Lemmy community hasn’t quite caught up yet, and now there is a transitional period where the audience is smaller.