Thursday 02 August 2007 8:11:52 pm
Assuming the user input is just user data, without additional information, it is really similar to a flat file and the import is fairly straightforward. I have run many imports on eZ, with many types of content and some of my ideas are: Backup the database Break the import into chunks, so if something goes wrong, recovery is easier Remember that an import tends to be a one-shot event, usually the code only has to run once, so it can be simple, brute force code. Often converting it to a convenient format is as much work as the import itself, thus custom code may actually be more cost-effective than pursuing a more flexible tool. I do agree a standardized import would be nice, but in this case, I think a simple utility is fine.
|