RE: [mv] 3.14-4.04 Migration Confusion

[Barney Treadway <barney@wttech.com>]

******    message to minivend-users from Barney Treadway <barney@wttech.com>     ******

Many thanks Cameron,

I have done as you suggested (deleting all file.sql) and the errors
continue, and erratic as well which makes diagnosis difficult. I dropped all
tables and _including_ the mv_test_create and get part way through this.
Sometimes it appears to choke creating users, sometimes shipping.. this is
the last try log (edited for list sanity!)

[usr145@widgr0003atl2 mvend]$ bin/restart
Killing Minivend server 1282 with TERM.
Low traffic settings.
MiniMate is NOT active.
MiniVend V4.04
Configuring catalog demo...
Using MySQL for databases, DSN=dbi:mysql:demo.

ConfigDatabase scalar parameter USER redefined to 'myuser', was myuser.
In line 4 of the configuration file 'mysql/pricing.mysql.old':
Database  pricing  USER         __SQLUSER__

ConfigDatabase scalar parameter PASS redefined to 'mypass', was mypass.
In line 7 of the configuration file 'mysql/pricing.mysql.old':
Database  pricing  PASS         __SQLPASS__

ConfigDatabase scalar parameter KEY redefined to 'sku', was sku.
In line 9 of the configuration file 'mysql/pricing.mysql.old':
Database  pricing  KEY          sku

table userdb created: create table userdb (
username char(16) NOT NULL,
...snip...
and on and on, apparently correctly
..snip...
)

bad table creation statement:
create table pricing (
q2 CHAR(12),
price_group CHAR(2) DEFAULT '' NOT NULL, index(price_group),
sku CHAR(9) NOT NULL PRIMARY KEY,
q5 CHAR(12),
q10 CHAR(12),
q25 CHAR(12),
q100 CHAR(12),
XL CHAR(12),
S CHAR(12),
red CHAR(12)
)


Error: Table 'mv_test_create' already exists
demo config error: Can't call method "set_row" on an undefined value at
(eval 49
) line 7, <IN> chunk 2.

-------------
Again, mv_test_create was dropped before restart, so it shouldn't have
"existed".

BTW, I don't use minimate at all. Nothing against minimate, we're just
building our own php version due to our particular needs.

In previous restart I got this one, but the above seemed to finish shipping
and user tables and proceed. In fact it appears if I drop mv_test and
restart, each time I seem to get one more table created. I'm certain this
isn't optimal....

In line 9 of the configuration file 'mysql/pricing.mysql.old':
Database  pricing  KEY          sku

bad table creation statement:
create table shipping (
..snip..
formula VARCHAR(128),
opt TEXT
)


Error: Table 'mv_test_create' already exists
demo config error: Can't call method "set_row" on an undefined value at
(eval 48
) line 7, <IN> chunk 2.

Going crazy here, if someone else has been through this hell, please show me
the exit.

>
> ******    message to minivend-users from "Cameron B. Prince"
> <cbp@InternetExpertsLLC.com>     ******
>
> Hi Barney,
>
> When I converted I had similar errors at times. I finally found that in my
> particular case, using MiniMate's spreadsheet function was at
> least part of
> the problem.
>
> It was somehow corrupting the tables in mysql and the only way I
> was able to
> fix them was by deleting each of the .sql files in the products directory
> and the corresponding database files in /var/lib/mysql... the
> restarting so
> the databases were recreated.
>
> Mike Heins recently did report that he knew of the problem and advised
> against using the spreadsheet function.
>
>
> ******    message to minivend-users from Barney Treadway
> <barney@wttech.com>
> ******
>
> Greetings all,
>
> Having a heck of a time getting mysql going on mv 4.04. All my blood and
> tears invested in 3.14 isn't paying off because of the small differences
> between the catalog.cfgs (supposedly). 4.04 created shipping and userdb in
> sql, but doesn't appear to be using them. I kept getting mysql
> syntax errors
> (table creation) during reconfig so I manually created all tables
> and placed
> empty tablename.sql files in products and I'm back to the:
> "demo config error: Directive ProductFiles returned default setting error:
> No default search file!"
>

-
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