top | item 47089531 (no title) jmalicki | 9 days ago One trick I learned for this was to use csv for LLM I/I and translate json <-> csv at the boundary layer discuss order hn newest fumeux_fume|9 days ago Oh neat. So have the llm output csv instead of JSON and then convert it? How would handle nested structures? jmalicki|9 days ago Depending on how it's nested, you could denormalize, think of how you could denormalize a one-to-many SQL relationshipSo if you have a user that has many automobiles, maybe instead of Autos: [...] you could do Auto1Make Auto2Make etc.
fumeux_fume|9 days ago Oh neat. So have the llm output csv instead of JSON and then convert it? How would handle nested structures? jmalicki|9 days ago Depending on how it's nested, you could denormalize, think of how you could denormalize a one-to-many SQL relationshipSo if you have a user that has many automobiles, maybe instead of Autos: [...] you could do Auto1Make Auto2Make etc.
jmalicki|9 days ago Depending on how it's nested, you could denormalize, think of how you could denormalize a one-to-many SQL relationshipSo if you have a user that has many automobiles, maybe instead of Autos: [...] you could do Auto1Make Auto2Make etc.
fumeux_fume|9 days ago
jmalicki|9 days ago
So if you have a user that has many automobiles, maybe instead of Autos: [...] you could do Auto1Make Auto2Make etc.