Manticore Team

➤ PavelShilin89 commented: Indeed, **RELOAD TABLES** helped solve the problem. The problem was that I was running **searchd** and **indexer** in the wrong order.

➤ Sergey Nikolaev commented: Please provide more details about the issue.

➤ Nick Sergeev commented: I've added the details to the issue's body.

➤ Ilya Kuznetsov commented: We will also need to add specializations for range filters to replace the generic `if ( RANGE_EVAL::Eval ( (VALUES)i, (VALUES)m_iMinValue, (VALUES)m_iMaxValue ) )` that we have...

➤ Nick Sergeev commented: The information on this feature is now added to the documentation: https://manual.manticoresearch.com/dev/Adding_documents_to_a_table/Adding_documents_to_a_real-time_table#Auto-schema

➤ Ilya Kuznetsov commented: Unable to reproduce in latest master `Manticore 5.0.3 58d6038fb@230114 dev (columnar 1.16.1 7fec1ab@230114) (secondary 1.16.1 7fec1ab@230114)`. There's no crash with or without `pseudo_sharding`. There's also no...

➤ Aleksey N. Vinogradov commented: That is wrong guess. Create table saves indexes ok, however after a crash we resurrected with original index table inherited from watchdog, which never refreshed.

➤ Nick Sergeev commented: We've opened another [issue](https://github.com/manticoresoftware/manticoresearch/issues/1279) about the subject so we close this one.

➤ Nick Sergeev commented: Yes, it works with dbForge now, but the issue about MySQL Workbench still remains.