You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 13, 2022. It is now read-only.
About 6 years ago I wrote a module (pgImport) that imports, or perhaps rather synchronizes, data in an external database with the publications belonging to a specific publication type. Perhaps a similar facility would be valuable in pagemaster? Or perhaps in a separate pmImport module?
The admin interface allows defining a connection string, primary key, username, password, email address for reporting problems, and a switch to allow for (cron based) automatic synchronizing. Furthermore there is a facility to map selected elements in the SQL query to pagesetter fields.
The module keeps an md5 hash of the contents of each query result linked to the primary key and thus decides if a publication needs to be created, updated, or deleted. -dits
The text was updated successfully, but these errors were encountered:
I would just like to add my support for this ticket. I was looking through the ticket list to add this exact request and found this ticket instead. This is exactly what I need for a few projects. I think it would be very handy for any enterprise company or small business who may have other DB's they can grab data from.
This would be an awesome feature. -Steven
Many are considering how to import pagesetter, pagemaster-data. Most data exist in other formats (xls,google.docs,CSV etc.alt.)
This could be a most common approach importing data into clip.
Of course I can do that with tools like HeidiSQL or other.
Opening Clip for import-formats (stepbystep) would open the module for a wide range of users.
Very interesting idea!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
About 6 years ago I wrote a module (pgImport) that imports, or perhaps rather synchronizes, data in an external database with the publications belonging to a specific publication type. Perhaps a similar facility would be valuable in pagemaster? Or perhaps in a separate pmImport module?
The admin interface allows defining a connection string, primary key, username, password, email address for reporting problems, and a switch to allow for (cron based) automatic synchronizing. Furthermore there is a facility to map selected elements in the SQL query to pagesetter fields.
The module keeps an md5 hash of the contents of each query result linked to the primary key and thus decides if a publication needs to be created, updated, or deleted. -dits
The text was updated successfully, but these errors were encountered: