If no export/import feature then what about a "helper" plugin?

4 posts by 2 authors in: Forums > CMS Builder: Plugins & Add-ons
Last Post: September 28, 2009   (RSS)

By Codee - September 22, 2009

Dave and Co.,
I know you've received numerous requests for an import/export feature over the years and that's a really hard "generic" programming project because everyone's database, even on similar projects, can be so different. I can see resultant nightmares from non-custom programming on something like this. So I've been thinking, especially for beginners or for projects that farm out to others...what about a "helper plugin" for this feature that essentially prints out a form with all the database fields that will be necessary for importing/exporting? It reads the current database, because the tables/fields can change often, and gives a proprietary list for that database that the project manager or programmer, maybe even novices, can use to create their own import/export scripts. I hope I'm being clear on this and hope it's not too stupid of a suggestion.

Re: [equinox69] If no export/import feature then what about a "helper" plugin?

By Dave - September 28, 2009

Hi Terry,

Thanks for the suggestion. Yes, that would probably be a good place to start.

We have "CVS Import" on our list of plugins to build so we'll have to see what other challenges come up when we get to it. One of the other issues is what to do with record numbers (create new numbers, or overwrite existing numbers) and records (add to database or erase existing data).

We'll probably see this in the next few rounds of plugins which we're working on.
Dave Edis - Senior Developer
interactivetools.com

Re: [Dave] If no export/import feature then what about a "helper" plugin?

By Codee - September 28, 2009

Thanks Dave,
One of the other issues is what to do with record numbers (create new numbers, or overwrite existing numbers) and records (add to database or erase existing data).

Yep, that's one of the prospective nightmares. Whomever is doing the import/export needs to decide how they want this handled (probably on an each case basis). If they're writing the script then they'll have to be mindful of this OR if it's possible for a plugin, then what would be great is a way to choose which method...either an overwrite, an addend, or "check for same record and overwrite if same, and addend the rest" feature.

I've dealt with quite a few classifieds companies, and this always seems to be a rough process, mostly because of matching to field names and field types between the database files. Maybe a feature that checks compatible field names (et al: "this field in file A" equals "this field in file B" ) and ensures compatible data types (so lists aren't loaded as graphic files, etc.) and the import/export is canceled if something doesn't match - to avoid database corruptions.


Have a great day!