Editing Database package
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 12: | Line 12: | ||
** [https://github.com/rmartinjak/mex-sqlite3 mex-sqlite3] – An extension for MATLAB® or GNU/octave to access sqlite3 databases | ** [https://github.com/rmartinjak/mex-sqlite3 mex-sqlite3] – An extension for MATLAB® or GNU/octave to access sqlite3 databases | ||
** [https://github.com/Andy1978/octave-sqlite octave-sqlite] - sqlite3 wrapper as an .oct file for GNU/Octave | ** [https://github.com/Andy1978/octave-sqlite octave-sqlite] - sqlite3 wrapper as an .oct file for GNU/Octave | ||
* '''redis''' | * '''redis''' | ||
** [https://gitlab.com/markuman/go-redis go-redis] - mex file extension for GNU/Octave to access Redis | ** [https://gitlab.com/markuman/go-redis go-redis] - mex file extension for GNU/Octave to access Redis | ||
Line 19: | Line 18: | ||
==Installation== | ==Installation== | ||
Requires octave struct, libpq-dev, and liboctave-dev. In ubuntu/debian based systems this is handled with | Requires octave struct, libpq-dev, and liboctave-dev. In ubuntu/debian based systems this is handled with | ||
apt install octave-struct libpq-dev liboctave-dev | apt install octave-struct libpq-dev liboctave-dev | ||
Line 42: | Line 39: | ||
conn = pq_connect (setdbopts ("dbname", "mydatabase")); | conn = pq_connect (setdbopts ("dbname", "mydatabase")); | ||
Here, you are specifying a key-value pair. So you want to fill in a key (dbname), and that dbname is mydatabase. | Here, you are specifying a key-value pair. So you want to fill in a key (dbname), and that dbname is mydatabase. | ||
Now, you are ready to read the db: | Now, you are ready to read the db: | ||
N = pq_exec_params (conn, "select * from Table1;") | N = pq_exec_params (conn, "select * from Table1;") | ||
Line 100: | Line 89: | ||
===Cell2mat: Database Data Types Should be the Same=== | ===Cell2mat: Database Data Types Should be the Same=== | ||
Note that you must have all database columns be the same type in order for the values to not get potentially changed when using cell2mat. In the example above, if you have the UnixTime column above be a bigint, and the Value column be an Int, the UnixTime will get truncated. Changing the Value column to a bigint will resolve this. | Note that you must have all database columns be the same type in order for the values to not get potentially changed when using cell2mat. In the example above, if you have the UnixTime column above be a bigint, and the Value column be an Int, the UnixTime will get truncated. Changing the Value column to a bigint will resolve this. | ||
==Further Reading== | ==Further Reading== |