Lauris BH

Yes, migration and doctor fix would be nice for this

I think it would be good idea to make it sticky only if toc height is less than screen height by adding custom class on load with js

I think only PostgreSQL and MSSQL support this, tho I have not used MSSQL for quite some time already :)

First step would be probably just implement for ones who support schemas and for others just print warnings Maybe for MySQL and sqlite3 use schema as prefix for table names?

If you want to use multiple schemas in single app search_path is not very useful. Migration is just one part - if adapter does not support it can just ignore...

There will be problem handling this in adapters if only Table() is used as in sqlite and mysql schema should be used as prefix instead.

But how would you specify that selects (except for update) go to one set of connection and inserts, updates, deletes and selects with for update to other?

if Query/Aggregate is run in transaction or Query has `rel.ForUpdate` it must also use primary

I mean if I start transaction and do insert/update etc any SELECTS that are done within that transaction should be done within same transaction using same connection

Shouldn't it also check context in [here](https://github.com/go-rel/primaryreplica/blob/main/primary_replica.go#L96) to see if in transaction and return primary if it is