![]() The real value is that you could actually query the data from within Postgres then join across your data stores, without having to do some ETL process to move data around. SQL is an expressive language, though people are often okay with accessing Mongo data through its own ORM. ![]() While this is powerful I think much of the true value was entirely missed within the post. Yesterday there was a post which hit Hacker News that talked about using SQL to access Mongo. This is currently a very lightweight utility that allows you to flip your site into two modes. Though just in talking with Simon about this a week ago it occurred to me they had not released the code for their read-only mode.įinally onto the announcing, today I’m releasing django-db-tools. Andrew Godwin further talks about some of this as well in regards to the Lanyrd move and even includes the script they used to migrate data from MySQL to Postgres. By having the ability to turn your site into a read only mode which Simon Wilson talked about in his post on Lanyrd you can still continue to operate just in a limited capacity. In these cases the default approach is to just schedule downtime often throwing up a splash screen saying so.įor many sites this approach is simply wrong and lazy, with little effort you can improve the experience and there by ease the burden in conducting these types of migrations. I dont mean simple add a column here or add an index there, but rather truly sizeable migrations… Going from MySQL to Postgres or migrating from an older version of Postgres such as a 32 bit instance to a newer 64 bit instance. For now I live in a work where I’m quite content with simple ole psql here’s how:įor any successful web application there is likely to come a time when you need to conduct some large migration on the backend. If you’re interested in helping build those to make the community better please reach out. ![]() > Seq Scan on users (cost=0.00.3.00 rows=100 width=27) (actual time=0.007.0.042 rows=100 loops=1)Įmpowering more developers by surfacing this information in a digestable form, such as building on top of pg_stat_statements tools such as datascope by and getting this to be part of the default admin we will truly begin empowering a new set of user.īut enough of a detour, those tools aren’t available today. Even with all of the powerful stats being captured in the statistics of PostgreSQL so many are still terrified when they see something like: QUERY PLAN pg_stat_statements was a great start to this laying a great foundation for valuable information being captured. First this is not a knock on the work thats been done on previous ones, for their time PgAdmin, phpPgAdmin, and others were valuable tools, but we’re coming to a point where theres a broader set of users of databases than ever before and empowering them is becoming ever more important.Įmpowering developers, DBA’s, product people, marketers and others to be comfortable with their database will lead to more people taking advantage of whats in their data.
0 Comments
Leave a Reply. |