Jump to content


  • Content count

  • Joined

  • Last visited

1 Follower

Profile Information

  • Real Name
    Tim Gales
  1. Iain, have you found a solution to this yet? If you're running a Linux machine, use the SED command to replace ** with EOREOR, and use carriage returns (\n) as your field delimiter in Easy Populate. sed 's/\*\*/EOREOR/' your_text_file.txt > new_text_file.txt Tim
  2. The products_id is generated by MySQL as an auto-increment field. Its purpose is to tie multiple osCommerce tables together, but outside osCommerce is has no usefulness as there's no way to tie it to a product. I looked at products extra fields, and while it does make adding more detailed product information nice and easy, it's fairly inefficient. I ended up just adding columns to the products table and everything works out much better. If you have a product detail you'd like to add with a small number of values that are common to many products, you could duplicate the functionality of the manufacturers and manufacturers_info tables. Tim
  3. Jeff, stock osCommerce doesn't have a "products_stock" table, and stock Easy Popluate doesn't look for that table either. If the code is looking for this table, something must have been modified. Are you running a Linux or Windows server? On Linux I would suggest running a 'grep -l -r "TABLE_PRODUCTS_STOCK" *' command to find out where that table is defined, and which pages are looking for it. You also mentioned that you're running version 3 of Easy Populate, which has been "disowned" by the author himself. I would suggest using an older version (between 2.8 and 2.9) that stores the configuration variables in the database like most other user friendly contribs. Tim By the way, I have a HUGE inventory, and to import and update 100,000 products using a heavily modified Easy Populate (it updates a lot more columns in the database, automatically updates pricing according to a table defined through the admin section, updates inventory hourly and checks for new products weekly through cron), it only takes SIX MINUTES to update every field!
  4. Hugh, I'm glad you like my fix. I'm afraid I have to point out that while an index can be unique, that is only the case if you explicitly define it to be. An index can use the optional flags UNIQUE, FULLTEXT, or SPATIAL. The whole point of a MySQL index is to prevent a search from reading the entire row. It's like creating a compressed version of the table with only one column. Since the products table contains a lot of columns (and I've added a few on my custom install), I really don't see any down side to indexing the model column. The speed increase for Easy Populate should go up logarithmically for every column it doesn't have to read when searching to see if a product already exists. Tim