Context Navigation

Changes between Initial Version and Version 1 of Ticket #14558, comment 41

initial	v1
1	1	After all these years, Im now 50/50 on this. The backwards compatibility concerns are major, and even if the custom post types are redirected to another table, that table would also choke when millions of rows were inserted to it anyway. So there may not be much gain from doing this since the performance concerns would need to be addressed eventually in either case.
2	2
3		However, having the ''possibility'' of redirecting all db operations for any given post type to another table could work and it could address both the backwards compatibility concern and the performance concern with custom post type setups with millions of rows. Ie, if an arg is supplied in ~~custom post definition for a different table, WP redirects all db operations for that post type to other tables~~ than wp_post and wp_postmeta etc. This could be made happen in other ways of course, this is just an idea...
	3	However, having the ''possibility'' of redirecting all db operations for any given post type to another table could work and it could address both the backwards compatibility concern and the performance concern with custom post type setups with millions of rows. Ie, if an arg is supplied in a custom post definition to use a different table, WP redirects all db operations for that post type to other tables rather than wp_post and wp_postmeta etc. This could be made happen in other ways of course, this is just an idea...