Explore >> Select a destination
|
You are here 
|
neo4j.com | ||
| | | | |
maxdemarzi.com
|
|
| | | | | Data is everywhere... all around us, but sometimes the medium it is stored in can be a problem when analyzing it. Chances are you have a ton of data sitting around in a relational database in your current application... or you have begged, borrowed or scraped to get the data from somewhere and now you... | |
| | | | |
www.llamaindex.ai
|
|
| | | | | LlamaIndex is a simple, flexible framework for building knowledge assistants using LLMs connected to your enterprise data. | |
| | | | |
dylanpaulus.com
|
|
| | | | | PostgreSQL (Postgres), is a powerful relational database that can store a wide range of data types and data structures. When it comes to storing graph data structures we might reach for a database marketed for that use case like Neo4J or Dgraph. Hold your horses! While Postgres is not generally thou... | |
| | | | |
blog.julik.nl
|
|
| | | We get attached to code - sometimes to a fault. Old migrations are exactly that. They're digital hoarding at its finest, cluttering up your codebase with files that serve absolutely no purpose other than to make you feel like you're preserving some kind of historical record. But here's the brutal truth: your old migrations are utterly useless. They're worse than useless - they're actively harmful. They're taking up space, they are confusing (both for you and new developers on the project), and they give you a false sense of security about your database's evolution. If your database is out-of-sync with schema.rb you need to solve that problem anyway, and - if anything - the migrations make that problem worse. | ||
