trying to update items

[njlinus]

hey guys, i have a fresh install with the new serverpack I am using AX database. when i try to update the items i realized a few things that might just be my problem but i figured id see if anyone else is having the same problems.
When putting the load_13thfloor_items.pl file into perl..i cant find it in the source folder in mt eqemu directory
I got an older copy i had and when trying to run the
"perl load_13thfloor_items.pl -d eqemu_config.xml <items.txt"
command i get an error(could be because i got a different load13thfloor file)
the error is "invalid db.ini, missing one of:Host,user,password,database


here is my db.ini
###Your current database configuration is as follows:
##db.ini:

[Database]
host=localhost
user=eq
password=eq
database=ax


thanks in advance
Brad

[sesmar]

This may sound like I am pointing out the obvious here but your db.ini file is in the same directory that you are running the perl script from?

[njlinus]

I followed the directions in the wiki and copied the db.ini to the c:\perl folder

[bufferofnewbies]

try useing ax_peq instead of ax, and see if that works.

[njlinus]

Just tried ax_peq and got the same message. ill keep trying, it has to be something

[cavedude]

The database is ax in the installer, and there shouldn't be a need to update the items, they are the newest.

[bufferofnewbies]

Originally Posted by cavedude

The database is ax in the installer

ahh, totally my bad. For some reason I always had it as ax_peq. Must have been something I did to keep them seperated and merely forgot that I did it.

I tend to do that alot..

[cavedude]

By default the database installs itself as ax_peq, but for the installer pack I shortened it to just ax since I believe Angelox's is a database to its own and doesn't need the PEQ name in front of it.

[bufferofnewbies]

whew, so I'm not totally as senile as I thought..

[John Adams]

Originally Posted by bufferofnewbies

whew, so I'm not totally as senile as I thought..

Well, let's not get hastey.

[njlinus]

thanks for the replies, When searching the 13thfloor for items i noticed some of the items werent coming up in eqmu so i figured i needed to update my items.
thanks

[bufferofnewbies]

careful about loading some of the items, if you dont have the sv corruption field.

Not sure what all is in the system, as Im lazy and rarely look (bad DM, bad!) but if the items arent compatable with your current database setup, it will error them out.

13th floor adds items from live, so they use the current live fields. Our database may/ may not be up to date with those, since that save field isnt necessary for Titanium atm.

Ignore this if we do have it. I guess I should go check before I open my big mouth..

[John Adams]

I am almost certain you can add the new columns for the newer 13th floor stuff to your eq database. The server shouldn't care, cuz if we do a select *, it'll only use what it needs... and in many cases, I see us do a select [field-list] anyway, so again, newer columns *should* be ignored. The problem will come in writing TO the database - if we do not provide the exact field names for our VALUES () statement.

Ie., INSERT INTO items (field-list) VALUES (values);

Without the field-list on an insert, you will get invalid column count errors. But reading should be ok.

[sesmar]

The problem with the 13th floor items, at least from pre-DoN to post-DoN was that some of the field mappings had changed. Also the perl script used to read the file did not know how to insert all the fields into the database correctly because of this. Another issue that may arise is using the perl script to insert the 13th floor items into a server using MySql 5. I do not know if this problem has been fixed but the load items script would not work with MySql 5 when I last tried but it would load them into MySql 4 with out a problem.

[John Adams]

Sesmar, could your mySQL 5 problem related to "strict mode"? Just a thought.

...and I forgot the 13th floor stuff is loaded via perl script. That script would have to be edited to match columns, then. Sounds like it isn't written that way currently.