<FromGitter>
<ZeroPointEnergy> Is there a clever way to check the shard dependencies for updates without checking the github repos manually for new releases?
<FromGitter>
<eliasjpr> It looks like is addressing the issue. @drujensen in regards to the granite PR above. I think that there should only be a single connection per Granite instance, rather than per Granite::Model instance. It would be great to load test that branch
<robacarp>
@zeropointenergy there really isn't at the moment. there was a website which did the the calculation as a service, but I believe it's defunct
<FromGitter>
<Blacksmoke16> im pretty sure i had a PR to make it one connection, but was using multi connection for performance reasons
<FromGitter>
<Blacksmoke16> but there kinda needs to be at least one connection per model, in that if you have 3 models using 3 diff adapters they would each require a separate connection
<FromGitter>
<Blacksmoke16> but if two are using the same you *could* have one connection that both use i guess?
<FromGitter>
<Blacksmoke16> vs each one having their own
<FromGitter>
<paulcsmith> If each model has it's own connection it may be difficult to group saves to multiple models in one transaction as well. I'm not sure but it seems like that may be the case
<robacarp>
Yeah, I think connections should be pooled by adapter name, and all models using that adapter should fetch from the same pool
<FromGitter>
<paulcsmith> 👍 Yeah that sounds like a good way to handle it
<robacarp>
there's something subtle about using only one connection per request...I can see how that'd be helpful, and how it'd be a problem
<robacarp>
but transactions definately have to come through the same connection (I don't think we have any support for transactions anywhere in granite or amber)
<FromGitter>
<eliasjpr> @robacarp that’s what I would expect and we do not have to handle the pool since the crysta-dB shard does that