Davide Alberani wrote: > Now, the question is: is there a (more-or-less) universal format of > CSV file accepted by all/most-of the database servers out there? :-)
Since changing the code for formatting the CSV output should be quite easy if necessary, I think it is best to use an iterative approach. You could start with the CSV format specified in RFC 4180: <http://tools.ietf.org/html/rfc4180> (looks straightforward to me) At least DB2 seems to be quite flexible when it comes to importing CSV data: <http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/com.ibm.db2.luw.admin.cmd.doc/doc/r0008305.html> One important issue relevant to database import could be how auto-generated columns are handled (e.g. IDs): In DB2, the LOAD tool can be configured using the keywords "generated ignore" (columns to be generated by the database system are present in the CSV file but will be ignored/replaced) and "generated missing" (column to be autogenerated are not present in the CSV file). I think the latter approach looks better to start with in IMDbPY. Let's wait and see how other database system are handling this issue. Joachim -- M. Sc. Joachim Selke Technische Universität Braunschweig, Institut für Informationssysteme Mühlenpfordtstraße 23, 38106 Braunschweig, Germany <http://www.l3s.uni-hannover.de/~selke> ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Imdbpy-devel mailing list Imdbpy-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/imdbpy-devel
