Though sometimes it is nice to separate things out. Back in the java jdbc days, I'd always have to look up the exact url format for database connections because oracle's url connection string would be completely different from mysql, and still different from postgres.
> And mind you we are only talking about relational ones (the kind JDBC cares about).
It gets even more fun with Java EE where you can have arbitrary resource adapters. So then you have even non-SQL naming conventions to map within your application server.
Comments
Isn't this kind of obvious ?
Yes, but sadly this often gets overlooked. database.yml in Rails is a great example of that.
Though sometimes it is nice to separate things out. Back in the java jdbc days, I'd always have to look up the exact url format for database connections because oracle's url connection string would be completely different from mysql, and still different from postgres.
> because oracle's url connection string would be completely different from mysql, and still different from postgres
And that makes sense. At least a little. Because the way you use to locate a resource may vary wildly between databases.
And mind you we are only talking about relational ones (the kind JDBC cares about).
> And mind you we are only talking about relational ones (the kind JDBC cares about).
It gets even more fun with Java EE where you can have arbitrary resource adapters. So then you have even non-SQL naming conventions to map within your application server.