Update the documentation to remove dead bitbucket links

In the documentation some links are still pointing to the dead bitbucket wiki (at https://bitbucket.org/zzzeek/sqlalchemy/wiki/)

This is an example: https://docs.sqlalchemy.org/en/13/orm/extensions/baked.html#rationale

There is an example of this on the wiki in the section BakedQuery, a precursor to this feature …

I’m not sure if it is just a find https://bitbucket.org/zzzeek/sqlalchemy/wiki/ and replace https://github.com/sqlalchemy/sqlalchemy/wiki/ job. If so I can try to open a pr for it

[CaselIT]

The entry in that documentation page seems to be the only link to the bitbucket wiki.

Since you plan to rework the backed query anyway, and the is no longer the entry in the github page, I’ll leave it alone

[zzzeek]

bakedquery is getting a fair amount of use but the plan is hopefully that the whole thing would become transparent.

one of the biggest technical issues I’m having however is that to generate an “honest” cache key, which means, to actually look at all the expressions and parameters you put into the query and build up a cache key based on what is constructing the query, rather than “cheating” which is what the lambda thing is doing, is still fairly computationally expensive. the “lambda:” trick is still by far the most performant approach it’s just very strange looking. in the newer caching system, if I keep the lambda concept in, it will work even better because I’ve figured out a way to derive literal values from them. that is, you won’t need to worry about using bindparam() inside of them.

That probably all sounds very vague but it would take me a lot of time to explain, I hope that I can just get some time to make more progress with the newer approach.

if you need faster ORM queries right now I think you should use BakedQuery because the newer idea is not going to be production quality for at least a year.