These are chat archives for ManageIQ/manageiq/performance
find_by_*- those are reducing
ancestrycolumn parsing into a single source. So we can introduce multiple strategies. I really want arrays in there so we can see if that would make things like what @NickLaMuro is doing (string concatination of the ancestry string field so we can join into ancestrys in pure sql) in the db w/o funkyness
@Fryguy off hand, how do I know if I'm loading the database in schema load?
at class definition I want to mixin a different module.
I had used
connection - mistake. so we moved it to inside the lambda (not what I want)
It seems to be working for using
connection_config but I'm not positive that I didn't introduce db load at definition time again.
Ideas how to ensure I didn't just do taboo again?