legal "Selection Pattern" for migration job
On Thu, Mar 15, 2007 at 08:34:06AM +0100, Kern Sibbald wrote:
On Thursday 15 March 2007 02:09, Mike Seda wrote:
Is the following legal syntax for a migration job?
Selection Type = SQLQuery
Selection Pattern = "</var/bacula/migration-query.sql"
Where /var/bacula/migration-query.sql is a file that contains a single
sql command that returns a single jobId result?
No it is not valid. However, on the surface, it seems to be a good idea for a
feature request.
If I am not mistaken, the pattern can return any number of JobIds.
I've also been trying a few ideas with SQLQuery selection type for
migrations in 2.0.2 and mysql backend, but found that the mysql client
doesn't have the appropriate options (SELECT_MULTIPLE iirc is one of the
big ones, but the mysql manual just says that the client has to use
mysql 4.1 protocol) to allow the pattern to be thus:
Selection Type = SQLQuery
Selection Pattern = "CALL stored_procedure();"
Most of my toying with these things were due to 2.0.2's bugID 795
(PoolOccupancy returning MediaIds rather than JobIds) which has since
been fixed in 2.0.3 but I can see where other sites might want to do a
more complicated selection criteria where a stored procedure might be
easier on the db. I've also used a mysqldb view with some success to
help with some of the uglier crossjoins.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users < at > li...
https://lists.sourceforge.net/lists/listinfo/bacula-users
