[ic] re: NoImport Directives

Cameron B. Prince cameron@akopia.com
Thu, 12 Oct 2000 14:26:16 -0500

I have not used, and wasn't even aware of the existence of NoImportExternal.
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 to
have the database import. You use the .txt files as online, live backups of
your databases. Keep them up to date by using tag export in a receipt/report
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 restart.

Hope this helps,


-----Original Message-----
From: interchange-users-admin@minivend.com
[mailto:interchange-users-admin@minivend.com]On Behalf Of Houman Akhavan
Sent: Thursday, October 12, 2000 2:07 PM
To: interchange-users@minivend.com
Subject: Re: [ic] re: NoImport Directives


So then would NoImportExternal Yes be the equivalent of having a NoImport
line for every table.

Also, where should directives like this go in catalog.cfg at the top, or in
the #ifdef MYSQL, since I am using MySQL.

Does the syntax need a #, such as #NoImport products ?

Houman A.

----- Original Message -----
From: "Cameron B. Prince" <cameron@akopia.com>

> If the NoImport is added, it makes sense that no import would be
> Therefore, no .sql file, indicating a successful import, is made.
> You are simply telling Interchange to use the data in the database and
> disregard the corresponding .txt and .sql files.
> Good luck,
> Cameron

Interchange-users mailing list