RE: [mv] my mv4.0.3 makecat -> mysql hitch

[Michael Brian Bentley <bentley@crenelle.com>]

******    message to minivend-users from Michael Brian Bentley <bentley@crenelle.com>     ******

>******    message to minivend-users from Michael Brian Bentley 
><bentley@crenelle.com>     ******
>
>>I have used the mysql_setpermission perl script successfully, which 
>>comes with mysql and requires DBI and msql-Mysql-modules.
>>
>>-m
>
>However, restarting minivend after makecat makes a non-mysql simple 
>web site, I just noticed that the same error message comes up. 
>Something interesting goes on in one of the requisite modules I 
>added to perl 5.6.0 using cpan...?
>
>-m

Hi again. Yup, I've been spending far too many hours playing with 
this. At least I'm getting to know minivend and perl a little better, 
but on the whole I'd rather be editing tables and setting up layout.

I'm using the stock standard simple and the stock standard basic 
templates to create example sites, with one exception: my databases 
aren't named test_minivend.

The machine does appear to have all the requisite DBI and DBD mysql 
files installed. Mysql's set_permissions script works, and I've been 
able to get my "simple" web sites to populate the database with 
tables and fields when I use the delay to set a web site to mySql 
until after makecat has done its thing and I've had a chance to 
create an empty database manually in mysql.

I still get the following error message out of InMemory.pm, 
specifically the columns routine:

tweety config error: Can't use an undefined value as an ARRAY 
reference at /usr/local/ecom/mvend404/lib/Vend/Table/InMemory.pm line 
123.

I haven't figured out who is calling the columns routine in 
InMemory.pm that leads to my error message during startup, I've too 
green at perldebug ideosyncracies. (ok, _breakpoint_, darnit!)

Is there a perl routine call I can add, like Debugger(), that will 
cause perldebug to unarguably stop execution there if debugger is 
present? If I can do this, I'll be able to get a stack trace, and see 
what's what. Or, failing that, some idea what the magic formula is to 
set a working breakpoint at that routine? I've been doing things like

perl -d bin/minivend --start

And it does take me into perldebug, so I can step and set breakpoints 
and etc., but I seemingly aren't able to set a working breakpoint 
within InMemory.pm. I expect it has something to do with the module 
not being loaded/compiled...

The machine's perl 5.6.0 doesn't have either GDBM or DB_File installed.

I have installed a fresh minivend 4.04 a few times since my last 
note, with the problem persisting throughout.

-m

-
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