[mv] MV 4 beta 1 bug: .sql files created before successful table import

[Mark Stosberg <mark@summersault.com>]

******    message to minivend-users from Mark Stosberg <mark@summersault.com>     ******


I've got another issue to report with importing SQL tables. :)  When an
attempted import of a SQL database failed (done by restarting the
server), the .sql files for each database are being created regardless
of whether the table import was successful. In my opinion, the  .sql
files should only be created if the corresponding tables are
successfully created. Otherwise it gives the impression that there is an
accessible SQL table, when there really isn't. 

   -mark

MV beta 1
Postgres 6.5.3
-- 
  <<-------------------------------------------------------------->>
personal website                <    Summersault Website Design
   http://mark.stosberg.com/     >       http://www.summersault.com/
-
To unsubscribe from the list, DO NOT REPLY to this message.  Instead, send
email with 'UNSUBSCRIBE minivend-users' in the body to Majordomo@minivend.com.
Archive of past messages: http://www.minivend.com/minivend/minivend-list