I'm using Unicon database support with PostgreSQL on linux (without knowing much about odbc).
One of the database tables I'm operating on is set up with 'unique' columns to avoid duplicated rows. Now, I expect to try to insert lots of duplicated rows (the application is reading the syslogd log file and adding certain entries into the database - and I run it periodically to catch new log messages). My problem is that the failure to insert because of duplicated entries are generating *large* log files - for example, I just created a 8.8 MB log file on the last run (in a few seconds, no less!). The files are named like: /tmp/psqlodbc_sbw19356.log and since each has a unique name, they begin to pile up... Is there anyway through odbc initialization to turn off this logging? It's not the normal 'Trace' and 'Debug' odbc actions. Thanks for any help! Steve -- Steve Wampler ([EMAIL PROTECTED]) ------------------------------------------------------- This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en _______________________________________________ Unicon-group mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unicon-group
