Skip to content

Commit e09d152

Browse files
committed
Clarify documentation - was a bit misleading
1 parent ce0ab18 commit e09d152

File tree

1 file changed

+12
-3
lines changed

1 file changed

+12
-3
lines changed

README.md

+12-3
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,16 @@
1-
What?
2-
=====
1+
What can sql2json help you with?
2+
================================
33

4-
You need to transform a database from another vendor to another (e.g. MySQL -> PostgreSQL), or to just access the dataset programmatically?
4+
This project can help you if you need to:
5+
6+
- Export data from a database into JSON so it can be transformed to some other format more easily. E.g. you need to transform
7+
a database from another vendor to another (e.g. MySQL -> PostgreSQL). sql2json would help you get the data from MySQL into JSON
8+
and after that you could write a program to insert the data into PostgreSQL. This project doesn't help you with the actual
9+
transformation because it's not a trivial problem.
10+
11+
- Just dump the database contents to JSON so the JSON can be accessed from any programming language.
12+
13+
Why not just export SQL dump from vendor X and import the same file to vendor Y - SQL is standard anyways?
514

615
Turns out that SQL - even though being a standard, is not that interoperable. You cannot take a SQL dump produced
716
by say MySQL, and import it into SQLite or PostgreSQL. There are [clever hacks](https://gist.github.com/esperlu/943776),

0 commit comments

Comments
 (0)