<FromGitter>
<jaysneg> When it as property granite model not parse author_name data from pg response
<FromGitter>
<Blacksmoke16> right
<FromGitter>
<Blacksmoke16> whats the use case for wanting to skip it on save but not on read?
<FromGitter>
<Blacksmoke16> like if you're not saving it wont it always be like null/empty on read?
<FromGitter>
<jaysneg> Yes,skip it on save but not on read.
<FromGitter>
<Blacksmoke16> but why? wont it always be empty/null?
<FromGitter>
<Blacksmoke16> like if you're not saving it how would it be read?
<FromGitter>
<Blacksmoke16> oh i think i see, it comes from a joined table
<FromGitter>
<jaysneg> I am joins this field from another table
<FromGitter>
<Blacksmoke16> wouldnt a FK make more sense here? `post.user.name`?
<FromGitter>
<Blacksmoke16> and/or `user.posts`
<FromGitter>
<Blacksmoke16> because idt you can do what you want via Granite atm
<FromGitter>
<jaysneg> It make one request and your way will make much more
<FromGitter>
<jaysneg> I want to do this using joins but in docs did not find how to resolve this issue
<FromGitter>
<Blacksmoke16> > It make one request and your way will make much more ⏎ ⏎ There are ways around it
<FromGitter>
<Blacksmoke16> depends on what you're doing exactly
<FromGitter>
<Blacksmoke16> Granite doesnt have any way to preload/cache/prevent n+1 queries so thats on you atm
<FromGitter>
<Blacksmoke16> im sure theres some lower level stuff you could do to get what you want as well, but tl;dr idt theres a built in way to do what you want atm
alexherbo2 has quit [Ping timeout: 264 seconds]
<FromGitter>
<damianham> @jaysneg make your model a view - when I am querying the database with joins I always create view models for that purpose. e.g.