items import
Posted: Fri Mar 22, 2019 11:53 am
I am working on items import and will be ready for testing on my system this weekend, and hopefully ready to import into emu next week
i will be starting with simpler and smaller sets
first one i will be doing is bags there are only 399 total bags in census and we seem to have 354 of them
here is where i need input from developement team
1. Fact-- DO not want to change existing item id's( becuase that whould screw up so much effort and work on whats already in content
2. existing items that have changed stats
a. do we want the updated to the new stats
b. do we keep them at the stats they had when imported last time
* i will be doing a lookup of each item when i import on my system to see if it already exists in the db( based on SOE item id) if (a.) above then i will update the item with updated info from census. if (b.) above ill skip the item
3. if its a new item i will add the item to the db
once i confirm the new items are working as intendedi will then
if (a.) above export all item table to JAB so that he may meraculousy run the sql script to update the emu database for all items, this will keep existing itemids in tact so no changes to other systems will be necessarry
if (b.) above i will just export the new items and associated changes and to Jab for import
i do not plan on any db structure changes during this time
please let me know your thoughts
i will be starting with simpler and smaller sets
first one i will be doing is bags there are only 399 total bags in census and we seem to have 354 of them
here is where i need input from developement team
1. Fact-- DO not want to change existing item id's( becuase that whould screw up so much effort and work on whats already in content
2. existing items that have changed stats
a. do we want the updated to the new stats
b. do we keep them at the stats they had when imported last time
* i will be doing a lookup of each item when i import on my system to see if it already exists in the db( based on SOE item id) if (a.) above then i will update the item with updated info from census. if (b.) above ill skip the item
3. if its a new item i will add the item to the db
once i confirm the new items are working as intendedi will then
if (a.) above export all item table to JAB so that he may meraculousy run the sql script to update the emu database for all items, this will keep existing itemids in tact so no changes to other systems will be necessarry
if (b.) above i will just export the new items and associated changes and to Jab for import
i do not plan on any db structure changes during this time
please let me know your thoughts