##30/07/2024 An attempt was made to figure out current "Schema engine error: Connections using insecure transport are prohibited" as this was introduced when I shifted from cockroachdb to tidb for sql operations instead of postgresql operations. Turns out, now the db won't connect as I am supposed to be giving it a cert path which the documentation has failed to answer as to how to give it. At this point I wonder, should I transact the name search functionality( the leading cause of shifting ) for db successful connection. It's day 2 of this error, we met it yesterday. Now I might have to choose whether to spent my days into fixing this error or just switch back to postgresql. I a dis-connection with error, the only thing which bugs me are the number of days that will be spent upon it with no established stone to step on. What is the reason I should choose this option? Simply for the sake of making it better. I want to make this project work, in a way in which it compliments itself. I don't want to rip it off of search by name functionality because I was scared that how many days I am losing on this error which genuinly should'nt exist in the first place. I read it on reddit, that this was a one stop solution towards the lack of functionality that I was facing. And while setting it up, I felt the same. It had all the commands I chose not to write because postgres did not have them and since I chose postgres I have to stick to my choice. Maybe it's all about improvisation. Choose and Imporvise. I chose cockroachdb because planetscale isn't free anymore and it had mysql. I improvised and chose cockroachdb as it was free and I thought I was getting it as I was getting it. But lack of indexing made me feel I am not doing justice to this application as by switching to mysql will have make it better. But I chose to stay for a little longer to see where it goes.