Erik_
Just pulled a backup of current NEMB...data import
Tue Jul 16, 2019 10:35am
24.190.103.85

Should be able to import all the records from this disc app into the new one by using the SQL script they provide to load up a local DB with the current entries and then write a quick tool that just iterates through all the records of the backup table and inserts into the new disc app db with mapping the values to the correct destination tables/columns.

I'll definitely pull another backup closer to the shutdown date so nothing gets lost. I'll use this backup as a "safe" backup to write the tool and at the very least if for some reason the later backup does not work, we can fall back on this one.

I'm sure there's probably a way to do this is straight SQL by inserting using select but from what I see all hosting has a limit on how many rows you can have in your DB and it doesn't make sense to balloon up the final db (even for a short time) to possibly over the max allowed just for importing data.


Example of top of script to show the data structure. (Rest is just the insert of the raw text data)

DROP TABLE IF EXISTS `disc_46108`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `disc_46108` (
`id` mediumint(8) unsigned NOT NULL AUTO_INCREMENT,
`author` varchar(50) NOT NULL DEFAULT 'Anonymous',
`email` varchar(60) DEFAULT NULL,
`subject` varchar(64) NOT NULL DEFAULT '',
`date_entered` datetime NOT NULL,
`message` text NOT NULL,
`parent` mediumint(8) unsigned NOT NULL DEFAULT '0',
`ip` char(255) NOT NULL DEFAULT '',
`grandparent` mediumint(8) unsigned NOT NULL DEFAULT '0',
`threadactivity` datetime NOT NULL,
`personal_account` mediumint(8) unsigned NOT NULL DEFAULT '0',
`show_email` enum('0','1') NOT NULL DEFAULT '0',
`approved` enum('0','1') NOT NULL DEFAULT '1',
`bad_content` enum('0','1') NOT NULL DEFAULT '0',
`user_agent` char(128) NOT NULL DEFAULT '',
PRIMARY KEY (`id`),
KEY `parent` (`parent`),
KEY `grandparent` (`grandparent`)
) ENGINE=MyISAM AUTO_INCREMENT=21020 DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;

--
-- Dumping data for table `disc_46108`
--

LOCK TABLES `disc_46108` WRITE;
/*!40000 ALTER TABLE `disc_46108` DISABLE KEYS */;


  • Making some good progress on the disc app remake from the ground up. Currently main page pulls prologue, threads, config, etc from database based on application id in url. going to add epilogue now.... more
    • Just pulled a backup of current NEMB...data import ☻ Erik_, Tue Jul 16 10:35am
      • way there if the front end supports it.
        • Yeah looks to be!Erik_, Wed Jul 17 1:51am
          There's a few fields in their dump that I don't have in my database pertaining to show/hide email and stuff but I can add those in. Should all map to what I have pretty nicely! :) Still need to work... more
          • Although, did you reimplement future posting? I just noticed the form parameters were passed by GET and not POST. I don't see why he'd have a problem with it, shoot your code might even wind up being ... more
            • *Oh you did. :-) (nm)Puckdropper, Wed Jul 17 4:03am
              • On accident. :)Erik_, Thu Jul 18 4:53am
                Here's the current bugs/features I just threw together. Feel free to add more if you find any and feel like it. https://github.com/shamrice/discapp/projects/1
    • AWS deployment beta site (url inside)Erik_, Wed Jul 10 11:59am
      Deployed in AWS using postgresql instead of mysql. Here's a link to the test site: NEMB: https://shamricediscapp.herokuapp.com/indices/46108 Test: https://shamricediscapp.herokuapp.com/indices/1 If... more
Click here to receive daily updates
"Don't quote me." - Erik