Remove outmoded database drivers section

[amotl]

About

The drivers section was modernized and relocated. This patch removes the redundant outmoded one, where most items can easily be considered legacy and stale today.

After CrateDB received PostgreSQL compatibility, it gained a way larger surface of connectivity options, which is a good thing. At the same time, our legacy drivers became less maintained, which is natural. In this spirit, we shouldn't present them any longer on the main stage, but just refer to them within a larger gallery where other more optimal connectivity options exist, mostly through drivers and adapters which are NOT from our pen. ¹

References

• https://github.com/crate/tech-content/issues/124#issuecomment-3738490742

/cc @seut, @matriv, @surister

Footnotes

1. On the other hand, this absolutely doesn't mean they don't need maintenance dearly. The PHP drivers received a few cycles recently, but we don't even mention the legacy Ruby drivers there. Today, mostly the JDBC driver is in a sad state since ages. Please improve, so we can finally add and present Hibernate support, possibly on the main stage! ↩

[bmunkholm]

That's perfect.
I would suggest timing wise to just hold on a bit until the migration of the content of those drivers are merged into the Guide as Kenneth propose. There we can decide exactly which ones should be fully or partially merged.

[amotl]

Hi. I can't follow your rationale even when trying hard. All relevant refurbishments to the connect section have landed already. None of them include any comments or suggestions from your side, so please stop providing stop energy.

• Driver: Improve section about Java cratedb-guide#402
• Driver: Improve section about Python cratedb-guide#403
• Driver: Improve section about PHP cratedb-guide#404
• Driver: Add pages about C#, F#, Visual Basic cratedb-guide#409

[bmunkholm]

update: I hadn't seen your response to Kenneth when writing below. So let continue the alignment there.

---

I'm happy to explain the rationale if it's not clear from the discussion with @kneth here.
The point is that if we merge this right now:

1. The links in the Handbook connect section that points to "Documentation" will point to orphaned pages not present in any TOC

2. The content is still relevant, right? I assume that's why the current connect pages points to these pages via above "Documentation" links?

Is there any particular urgency to removing the "Database Drivers" section I'm not aware of? I'm hoping we can merge the drivers pages in very quickly. I just discussed that with Kenneth today.

[amotl]

The links in the Handbook connect section that points to "Documentation" will point to orphaned pages not present in any TOC.

Ah right, that's why we just can't remove the TOC. I am falling for that again and again. Apologies, blatantly removing the TOC / this primary navigation section is not applicable. Closing.

[kneth]

Apologies

Accepted.