[ic] re: NoImport Directives
Cameron B. Prince
Thu, 12 Oct 2000 15:16:17 -0500
I see the command there, but the docs describe NoImport.
If this is a global command, the databases wouldn't need to be specified.
I'll investigate this sometime.
[mailto:firstname.lastname@example.org]On Behalf Of Houman Akhavan
Sent: Thursday, October 12, 2000 3:06 PM
Subject: Re: [ic] re: NoImport Directives
Quoting mvdocs.pod line 13185
When set to one or more Interchange database identifiers,
those database(s) will never be subject to import. Useful for SQL
databases, or databases that will *never* change.
----- Original Message -----
From: "Cameron B. Prince" <email@example.com>
Sent: Thursday, October 12, 2000 12:26 PM
Subject: RE: [ic] re: NoImport Directives
> I have not used, and wasn't even aware of the existence of
> I did a quick search and didn't see that one in the docs... How did you
> learn about it?
> Just put all the databases on the line with products:
> NoImport products area cat orderline transactions
> It really doesn't matter where the command goes in the catalog.cfg. It can
> go inside the #ifdef MYSQL if you only want to prevent the import while
> using MYSQL.
> No # on directives, only conditionals.
> I am not sure I understand your reasoning here. It's normally beneficial
> have the database import. You use the .txt files as online, live backups
> your databases. Keep them up to date by using tag export in a
> or a cron job that runs a script, that in turn runs mysqldump -t and adds
> the header.
> Then if the database gets hosed, all you have to do is rm *.sql and
> Hope this helps,
Interchange-users mailing list