Jukka Raimovaara

yeah, there should be inheritAttrs: false, if there is v-bind="$attrs". or no v-bind, since they pretty much do the same thing.

I created a function to delete from compressed table using the segmentby col: https://gist.github.com/xvaara/81990e8291019f931387492c1869fe84 it has a lot of debug output, just comment out the notices when in production.

Still seems to be a problem for me on pg14 & ts 2.8.1. The difference for me is that I have a view on the compressed table and I'm selecting...

@svenklemm it seems it goes away if I vacuum full the table... also SET enable_indexscan to false; made it go away. It's some weird side effect that I can't reproduce,...

do we want to reimplement the bootstrap js in "native vue" or just use bootstraps own js like here: [https://dev.to/codeply/using-bootstrap-5-with-vue-js-5fnp](https://dev.to/codeply/using-bootstrap-5-with-vue-js-5fnp) There is also this: [https://github.com/superbvue/SuperBVue](https://github.com/superbvue/SuperBVue) and [material desin bootstrap](https://github.com/mdbootstrap/mdb-vue-ui-kit)

It might be complex to implement both bootstrap 4 and 5, there are differences in the class names. So every component would need two versions.

Just a quick hack using css filter: https://gist.github.com/xvaara/771d3c92a62d4149fa4e4b6d629b1b2b 

Could we just "massage" the $attrs to remove the class and put that to the root element. That would solve my problem and change as little as possible.

we could have: ```js const { class: rootClasses, ...attrs } = useAttrs(); ``` and use attrs instead of $attrs in input element, and add rootClasses to computedClasses: ```js const computedClasses...

The documentation is a bit unclear. The hide prop is for a middleware for hiding the popover when the reference leaves viewport: https://floating-ui.com/docs/hide show prop is to show the popover...