Joined: Aug 29, 2004 Posts: 7330 Location: Arizona
Posted:
Mon Jun 09, 2008 5:24 am
If you go to "Privileges", in there, you can elect to "Add New User". Once the user is added, you can then select that user from the Privileges list and then assign database-level permissions to it.
CREATE TABLE nuke_seo_feed (
fid int(6) NOT NULL DEFAULT 0 COMMENT '' auto_increment,
content varchar(20) NOT NULL DEFAULT '' COMMENT '' COLLATE latin1_swedish_ci,
name varchar(20) NOT NULL DEFAULT '' COMMENT '' COLLATE latin1_swedish_ci,
level varchar(20) NOT NULL DEFAULT '' COMMENT '' COLLATE latin1_swedish_ci,
lid int(6) NOT NULL DEFAULT 0 COMMENT '',
title varchar(50) NOT NULL DEFAULT '' COMMENT '' COLLATE latin1_swedish_ci,
`desc` text NOT NULL DEFAULT '' COMMENT '' COLLATE latin1_swedish_ci,
`order` varchar(20) NOT NULL DEFAULT '' COMMENT '' COLLATE latin1_swedish_ci,
howmany char(3) NOT NULL DEFAULT '' COMMENT '' COLLATE latin1_swedish_ci,
active int(1) NOT NULL DEFAULT 0 COMMENT '',
desclimit varchar(5) NOT NULL DEFAULT '' COMMENT '' COLLATE latin1_swedish_ci,
securitycode varchar(50) NOT NULL DEFAULT '' COMMENT '' COLLATE latin1_swedish_ci,
cachetime varchar(6) NOT NULL DEFAULT '' COMMENT '' COLLATE latin1_swedish_ci,
feedburner_address varchar(100) NOT NULL DEFAULT '' COMMENT '' COLLATE latin1_swedish_ci,
PRIMARY KEY (fid),
INDEX content (content, title)
) DEFAULT CHARSET=latin1 COLLATE=latin1_swedish_ci;
CREATE TABLE nuke_seo_subscriptions (
sid int(6) NOT NULL DEFAULT 0 COMMENT '' auto_increment,
type varchar(256) NOT NULL DEFAULT '' COMMENT '' COLLATE latin1_swedish_ci,
name varchar(60) NOT NULL DEFAULT '' COMMENT '' COLLATE latin1_swedish_ci,
tagline varchar(60) NOT NULL DEFAULT '' COMMENT '' COLLATE latin1_swedish_ci,
image varchar(256) NOT NULL DEFAULT '' COMMENT '' COLLATE latin1_swedish_ci,
icon varchar(256) NOT NULL DEFAULT '' COMMENT '' COLLATE latin1_swedish_ci,
url varchar(256) NOT NULL DEFAULT '' COMMENT '' COLLATE latin1_swedish_ci,
active int(1) NOT NULL DEFAULT 0 COMMENT '',
PRIMARY KEY (sid)
) DEFAULT CHARSET=latin1 COLLATE=latin1_swedish_ci;
ALTER TABLE nuke_authors
DROP INDEX aid;
ALTER TABLE nuke_autonews
DROP INDEX anid;
ALTER TABLE nuke_banned_ip
DROP INDEX id;
ALTER TABLE nuke_banner
ADD name varchar(50) NOT NULL DEFAULT '' COMMENT '' COLLATE latin1_swedish_ci AFTER cid,
ADD position int(10) NOT NULL DEFAULT '0' COMMENT '' AFTER dateend,
ADD ad_class varchar(5) NOT NULL DEFAULT '' COMMENT '' COLLATE latin1_swedish_ci AFTER active,
ADD ad_code text NOT NULL DEFAULT '' COMMENT '' COLLATE latin1_swedish_ci AFTER ad_class,
ADD ad_width int(4) NULL DEFAULT '0' COMMENT '' AFTER ad_code,
ADD ad_height int(4) NULL DEFAULT '0' COMMENT '' AFTER ad_width,
DROP type;
DROP TABLE nuke_bannerclient;
ALTER TABLE nuke_bbforums
DROP forum_parent;
ALTER TABLE nuke_bbsessions
DROP PRIMARY KEY,
DROP INDEX session_id_ip_user_id,
ADD INDEX session_ip (session_ip),
ADD INDEX session_id (session_id);
ALTER TABLE nuke_blocks
DROP INDEX bid;
DROP TABLE nuke_cities;
DROP TABLE nuke_clockcalendar;
ALTER TABLE nuke_comments
DROP INDEX tid;
ALTER TABLE nuke_config
ALTER minpass SET DEFAULT 8,
ALTER ultramode SET DEFAULT 1,
ALTER httpref SET DEFAULT 0;
DROP TABLE nuke_donators;
DROP TABLE nuke_donators_config;
DROP TABLE nuke_donators_settings;
ALTER TABLE nuke_downloads_categories
DROP INDEX cid;
ALTER TABLE nuke_downloads_downloads
DROP INDEX lid;
ALTER TABLE nuke_downloads_editorials
DROP INDEX downloadid;
ALTER TABLE nuke_downloads_modrequest
DROP INDEX requestid;
ALTER TABLE nuke_downloads_newdownload
DROP INDEX lid;
ALTER TABLE nuke_downloads_votedata
DROP INDEX ratingdbid;
ALTER TABLE nuke_encyclopedia
DROP INDEX eid;
ALTER TABLE nuke_encyclopedia_text
DROP INDEX tid;
ALTER TABLE nuke_faqanswer
DROP INDEX id;
ALTER TABLE nuke_faqcategories
DROP INDEX id_cat;
DROP TABLE nuke_g2config;
ALTER TABLE nuke_groups
DROP INDEX id,
ADD PRIMARY KEY (id);
ALTER TABLE nuke_groups_points
DROP INDEX id,
ADD PRIMARY KEY (id);
ALTER TABLE nuke_headlines
DROP INDEX hid;
ALTER TABLE nuke_journal
DROP INDEX jid;
ALTER TABLE nuke_journal_comments
DROP INDEX cid;
ALTER TABLE nuke_journal_stats
DROP INDEX id;
ALTER TABLE nuke_links_categories
DROP INDEX cid;
ALTER TABLE nuke_links_editorials
DROP INDEX linkid;
ALTER TABLE nuke_links_links
DROP INDEX lid;
ALTER TABLE nuke_links_modrequest
DROP INDEX requestid;
ALTER TABLE nuke_links_newlink
DROP INDEX lid;
ALTER TABLE nuke_links_votedata
DROP INDEX ratingdbid;
ALTER TABLE nuke_message
DROP INDEX mid;
ALTER TABLE nuke_modules
DROP INDEX mid;
ALTER TABLE nuke_nsnst_cidrs
MODIFY cidr int(2) NOT NULL DEFAULT 0 COMMENT '' auto_increment;
#
# Fieldformat of
# nuke_nsnst_cidrs.cidr changed from int(2) NOT NULL DEFAULT '0' COMMENT '' to int(2) NOT NULL DEFAULT 0 COMMENT '' auto_increment.
# Possibly data modifications needed!
#
DROP TABLE nuke_optimize_gain;
ALTER TABLE nuke_pages
DROP INDEX pid;
ALTER TABLE nuke_pages_categories
DROP INDEX cid;
ALTER TABLE nuke_poll_desc
DROP comments,
DROP INDEX pollID;
ALTER TABLE nuke_pollcomments
DROP INDEX tid;
ALTER TABLE nuke_public_messages
DROP INDEX mid;
ALTER TABLE nuke_queue
DROP INDEX qid;
ALTER TABLE nuke_quotes
DROP INDEX qid;
ALTER TABLE nuke_referer
DROP INDEX rid;
ALTER TABLE nuke_related
DROP INDEX rid;
ALTER TABLE nuke_reviews
DROP INDEX id;
ALTER TABLE nuke_reviews_add
DROP INDEX id;
ALTER TABLE nuke_reviews_comments
DROP INDEX cid;
DROP TABLE nuke_shoutbox_censor;
DROP TABLE nuke_shoutbox_conf;
DROP TABLE nuke_shoutbox_date;
DROP TABLE nuke_shoutbox_emoticons;
DROP TABLE nuke_shoutbox_ipblock;
DROP TABLE nuke_shoutbox_manage_count;
DROP TABLE nuke_shoutbox_nameblock;
DROP TABLE nuke_shoutbox_shouts;
DROP TABLE nuke_shoutbox_sticky;
DROP TABLE nuke_shoutbox_theme_images;
DROP TABLE nuke_shoutbox_themes;
DROP TABLE nuke_shoutbox_version;
ALTER TABLE nuke_stories
DROP INDEX sid;
ALTER TABLE nuke_stories_cat
DROP INDEX catid;
ALTER TABLE nuke_subscriptions
MODIFY userid int(10) NOT NULL DEFAULT '0' COMMENT '',
DROP INDEX id,
ADD PRIMARY KEY (id, userid);
#
# Fieldformat of
# nuke_subscriptions.userid changed from int(10) NULL DEFAULT '0' COMMENT '' to int(10) NOT NULL DEFAULT '0' COMMENT ''.
# Possibly data modifications needed!
#
DROP TABLE nuke_themecpanel;
ALTER TABLE nuke_topics
MODIFY topicimage varchar(20) NULL DEFAULT NULL COMMENT '' COLLATE latin1_swedish_ci,
DROP INDEX topicid;
#
# Fieldformat of
# nuke_topics.topicimage changed from varchar(100) NOT NULL DEFAULT '' COMMENT '' COLLATE latin1_swedish_ci to varchar(20) NULL DEFAULT NULL COMMENT '' COLLATE latin1_swedish_ci.
# Possibly data modifications needed!
#
ALTER TABLE nuke_users
MODIFY user_sig varchar(255) NULL DEFAULT NULL COMMENT '' COLLATE latin1_swedish_ci,
MODIFY bio tinytext NULL DEFAULT NULL COMMENT '' COLLATE latin1_swedish_ci,
MODIFY ublock tinytext NULL DEFAULT NULL COMMENT '' COLLATE latin1_swedish_ci;
#
# Fieldformats of
# nuke_users.user_sig changed from text NULL DEFAULT NULL COMMENT '' COLLATE latin1_swedish_ci to varchar(255) NULL DEFAULT NULL COMMENT '' COLLATE latin1_swedish_ci.
# nuke_users.bio changed from tinytext NOT NULL DEFAULT '' COMMENT '' COLLATE latin1_swedish_ci to tinytext NULL DEFAULT NULL COMMENT '' COLLATE latin1_swedish_ci.
# nuke_users.ublock changed from tinytext NOT NULL DEFAULT '' COMMENT '' COLLATE latin1_swedish_ci to tinytext NULL DEFAULT NULL COMMENT '' COLLATE latin1_swedish_ci.
# Possibly data modifications needed!
#
ALTER TABLE nuke_users_temp
ADD requestor varchar(25) NOT NULL DEFAULT '' COMMENT '' COLLATE latin1_swedish_ci AFTER time;
Now, if I click "send" it lets me download the SQL file. Im guessing if I click "switch" it will convert the DB for me. . . . or will it revert and backwards convert from rnuke2 to rnuke1? (im really not sure, I tried, and the tables look different).
Joined: Aug 29, 2004 Posts: 7330 Location: Arizona
Posted:
Fri Jun 13, 2008 5:56 am
ciph3r, the point of doing the comparison is not to have it make all the changes for you. If you run that SQL, you will remove a bunch of tables that you had in your original install (such as the shout box stuff). I guess its ok if you meant to go completely "clean", but the difference is to highlight things for your review.
Personally, I take down the sql and then go through it removing what I don't want/need. I would remove the CREATEs for anything prefixed with nuke_gcal_, nuke_hnl_ and nuke_seo_. For these, since they require also what I call "seed data", it would be better to just move the entire tables and their data over to your "old db".
In your original comparison settings, I would also set the "Alter charset" to "No".
Well, I got a 1 week paid vacation from work, and im wanting to get this done.
At this point, I want to test out all of the newest versions features from scratch.
I have the core RNUKE installed in XXAMPP, and all I want to do at this time, is import the forums, and the users.
The blocks, news. . . whatever else. . . i dont care about.
I can install the modules one at a time and work the bugs out then, but when it comes to just importing the forums. . . and users. . . what would it require?
I was thinking about just installing the old DB, and the new one in the phpadmin in xxampp, and then importing the tables for the forums and users. . . then running the rnuke upgrade script. . . . would that be ok?
Joined: Aug 29, 2004 Posts: 7330 Location: Arizona
Posted:
Thu Jun 26, 2008 5:10 am
No, I would keep off-line backups of both databases and then...
1. Use MySQLDiff to compare the two databases and produce the results.
2. Copy the SQL statements to a text file.
3. Edit that text file of SQL statements to remove anything that is not related to nuke_bb* and nuke_user*.
4. Apply the edited SQL file to your OLD database to make those tables MATCH the RavenNuke tables.
5. Export just those same tables' data from your OLD database now into your RavenNuke. You get some errors because of data already being in some of your RavenNuke Tables. You could actually remove the data from these same tables ahead of time (in the RavenNuke database) and try your import. I have a feeling that if you took all those mentioned tables, you should be ok in the end.
Good luck. And just remember, since you have off-line copies of both databases PRIOR to starting this effort, you can re-run this cycle as many times as you like until you get it right!
So far Ive got the source (rnuke1-old), and target (rnuke2-new) in mysqldiff.
I run it and get the results.
Ive read up on the mysqldiff site, and im a little confused at what im looking at.
Now, I know im looking at the structure of the database (the tables) but with those options checked. . . what exactly is this telling me?
These are all the tables in the rnuke2 db that are different from the rnuke1?
There just looks like to many differences:
For example:
In the new rnuke2 db, I have this:
Code:
nuke_banner_clients
In the old DB (rnuke1), I have this:
Code:
nuke_bannerclient
Is this something I must have screwed up during my original install of the old site, or is this an expected change?
The reason I ask, is because as stated above im not interested in the integrity of the rest of the site. . . since its a clean RNUKE install. . . I just want to keep my users and forums.
Now, im guessing this is what is needed to be changed in the old DB (rnuke1) to make it current with the latest RavenNuke core tables.
I didnt see any difference in the _bb_* sections of the database, except this:
Code:
ALTER TABLE nuke_bbforums
DROP forum_parent;
ALTER TABLE nuke_bbsessions
DROP PRIMARY KEY,
DROP INDEX session_id_ip_user_id,
ADD INDEX session_ip (session_ip),
ADD INDEX session_id (session_id);
Now, I know the 'DROP forum_parent;' was added when I did the SubForums mod. The nuke_bbsessions section, is what I need to add to the old rnuke1 database to make it current with what I want in the new install?
I have a migraine this morning so I have not fully digested this thread. I am assuming the objective is to convert the structureyour old database[b/] so you can then import the data from that into a new RN empty database?
If that is the case;
This is correct as stated above
ALTER TABLE nuke_bbsessions
DROP PRIMARY KEY,
DROP INDEX session_id_ip_user_id,
ADD INDEX session_ip (session_ip),
ADD INDEX session_id (session_id);
The table [b]nuke_banner_clients[/] in your NEW database is correct. The table was added to support the new advertising module.
The table [b]nuke_bannerclient in your OLD database is not required as it was dropped so there is no need to created that in the NEW database.
Joined: Aug 29, 2004 Posts: 7330 Location: Arizona
Posted:
Fri Jun 27, 2008 6:22 am
OH, one thing that I do is uncheck the CHARSET option in the list of options. It is better to not have that and your ALTER statements will be much more compact and readable.
View next topic View previous topic
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum