Removing Community Server database

Fixing typos in documentation.

L2J_DataPack/dist/sql/community/clan_introductions.sql

@@ -1,6 +0,0 @@
-CREATE TABLE IF NOT EXISTS `clan_introductions` (
-  `serverId` int(8) NOT NULL,
-  `clanId` int(8) NOT NULL,
-  `introduction` text NOT NULL,
-  PRIMARY KEY (`serverId`,`clanId`)
-) ENGINE=InnoDB DEFAULT CHARSET=utf8;

L2J_DataPack/dist/sql/community/comments.sql

@@ -1,10 +0,0 @@
-CREATE TABLE IF NOT EXISTS `comments` (
-  `serverId` int(8) NOT NULL DEFAULT '0',
-  `comment_id` int(8) NOT NULL DEFAULT '0',
-  `comment_ownerid` int(8) NOT NULL DEFAULT '0',
-  `comment_date` decimal(20,0) NOT NULL DEFAULT '0',
-  `comment_post_id` int(8) NOT NULL DEFAULT '0',
-  `comment_topic_id` int(8) NOT NULL DEFAULT '0',
-  `comment_forum_id` int(8) NOT NULL DEFAULT '0',
-  `comment_txt` text NOT NULL
-) ENGINE=InnoDB DEFAULT CHARSET=utf8;

L2J_DataPack/dist/sql/community/documentation.txt

@@ -1,3 +0,0 @@
-This directory contains tables required by the Community Server.
-
-Eventually, additional SQL scripts are locates in: custom/mods/updates folders.

L2J_DataPack/dist/sql/community/forums.sql

@@ -1,9 +0,0 @@
-CREATE TABLE IF NOT EXISTS `forums` (
-  `serverId` int(8) NOT NULL DEFAULT '0',
-  `forum_id` int(8) NOT NULL DEFAULT '0',
-  `forum_name` varchar(255) NOT NULL DEFAULT '',
-  `forum_post` int(8) NOT NULL DEFAULT '0',
-  `forum_type` int(8) NOT NULL DEFAULT '0',
-  `forum_owner_id` int(8) NOT NULL DEFAULT '0',
-  PRIMARY KEY (`serverId`,`forum_id`)
-) ENGINE=InnoDB DEFAULT CHARSET=utf8;

L2J_DataPack/dist/sql/community/posts.sql

@@ -1,14 +0,0 @@
-CREATE TABLE IF NOT EXISTS `posts` (
-  `serverId` int(8) NOT NULL DEFAULT '0',
-  `post_id` int(8) NOT NULL DEFAULT '0',
-  `post_ownerid` int(8) NOT NULL DEFAULT '0',
-  `post_recipient_list` varchar(255) NOT NULL DEFAULT '0',
-  `post_parent_id` int(8) NOT NULL DEFAULT '0',
-  `post_date` decimal(20,0) NOT NULL DEFAULT '0',
-  `post_topic_id` int(8) NOT NULL DEFAULT '0',
-  `post_forum_id` int(8) NOT NULL DEFAULT '0',
-  `post_txt` text NOT NULL,
-  `post_title` text,
-  `post_type` int(8) NOT NULL DEFAULT '0',
-  `post_read_count` int(8) NOT NULL DEFAULT '0'
-) ENGINE=InnoDB DEFAULT CHARSET=utf8;

L2J_DataPack/dist/sql/community/registered_gameservers.sql

@@ -1,6 +0,0 @@
-CREATE TABLE IF NOT EXISTS `registered_gameservers` (
-  `serverId` int(11) NOT NULL DEFAULT '0',
-  `hex_id` varchar(50) NOT NULL DEFAULT '',
-  `host` varchar(50) NOT NULL DEFAULT '',
-  PRIMARY KEY (`serverId`)
-) ENGINE=InnoDB DEFAULT CHARSET=utf8;

L2J_DataPack/dist/sql/community/topics.sql

@@ -1,8 +0,0 @@
-CREATE TABLE IF NOT EXISTS `topics` (
-  `serverId` int(8) NOT NULL DEFAULT '0',
-  `topic_id` int(8) NOT NULL DEFAULT '0',
-  `topic_forum_id` int(8) NOT NULL DEFAULT '0',
-  `topic_name` varchar(255) NOT NULL DEFAULT '',
-  `topic_ownerid` int(8) NOT NULL DEFAULT '0',
-  `topic_permissions` int(8) NOT NULL
-) ENGINE=InnoDB DEFAULT CHARSET=utf8;

L2J_DataPack/dist/sql/community/updates/20110316update.sql

@@ -1 +0,0 @@
-ALTER TABLE `posts` MODIFY `post_date` bigint(13) unsigned NOT NULL DEFAULT '0';

L2J_DataPack/dist/sql/community/updates/20110729update.sql

@@ -1,6 +0,0 @@
-ALTER TABLE `clan_introductions` ENGINE=InnoDB DEFAULT CHARSET=utf8;
-ALTER TABLE `comments` ENGINE=InnoDB DEFAULT CHARSET=utf8;
-ALTER TABLE `forums` ENGINE=InnoDB DEFAULT CHARSET=utf8;
-ALTER TABLE `registered_gameservers` ENGINE=InnoDB DEFAULT CHARSET=utf8;
-ALTER TABLE `posts` ENGINE=InnoDB DEFAULT CHARSET=utf8;
-ALTER TABLE `topics` ENGINE=InnoDB DEFAULT CHARSET=utf8;

L2J_DataPack/dist/sql/community/updates/cs_optimize.sql

@@ -1,6 +0,0 @@
-OPTIMIZE TABLE clan_introductions;
-OPTIMIZE TABLE comments;
-OPTIMIZE TABLE forums;
-OPTIMIZE TABLE registered_gameservers;
-OPTIMIZE TABLE posts;
-OPTIMIZE TABLE topics;

L2J_DataPack/dist/sql/community/updates/documentation.txt

@@ -1,6 +0,0 @@
-Any SQL Update should be named like this:
-
-YYYYMMDDupdate.sql
-
-For example, at day 5 and January 1 from 2008, then file should be named:
-20080105update.sql

L2J_DataPack/dist/sql/documentation.txt

@@ -1,4 +1,4 @@
-This directory contains tables needed for L2J "cs", ls and "gs" DataBases in order to run an L2J Server.
+This directory contains tables needed for Login Server and Game Server databases in order to run a L2J Server.
 
 Additionally, there are directories whose content serve different purposes.
 You should read documentation.txt files included inside these directories for further explanation about them.
@@ -18,7 +18,7 @@ In general, and unless otherwise stated by specific conventions or guidelines th
 - Since L2J supports MySQL as its one and only data management backend, we should not hesitate to introduce any standards extension or column type MySQL provides as a non-portable feature.
   This statement applies particularly when we could obtain any gain either from a readability, code maintenance or system performance perspective.
 
-- During data dump queries, no quotes should be used for numeric values and spaces after field separation commas should be ommited.
+- During data dump queries, no quotes should be used for numeric values and spaces after field separation commas should be omitted.
   This is in order to reduce file sizes.
 
 - Comments should be used at the developers discretion, to either serve as separators between structure and data, description of the ingame meaning of an statement or any other form of documentation intended to help administrators to understand the way they should use a table, or how could it be customized.

L2J_DataPack/dist/sql/maintenance/documentation.txt

@@ -1,4 +1,4 @@
-There are SQL sequences that should not neccessarily be performed every time you
+There are SQL sequences that should not necessarily be performed every time you
 update your database structure. Rather, these queries should be executed once or
 from time to time. Essentially, an .sql file should appear under 'maintenance'
 instead of the old 'updates' folder provided that:

L2J_DataPack/dist/tools/cs_cleanup.sql

@@ -1,14 +0,0 @@
--- These queries are meant to delete any communityserver table you may have from
--- previous L2J installations.
---
--- Queries that create these tables and/or populate them apropiately are
--- available in the ../cb_sql/ folder. See the documentation.txt file
--- for more details.
-
-DROP TABLE IF EXISTS
-clan_introductions,
-comments,
-forums,
-registered_gameservers,
-posts,
-topics;