Download Latest Version MP4public-v7.3.17.zip (2.1 GB)
Email in envelope

Get an email when there's a new version of Scorched Earth Online War

Home / sedb
Name Modified Size InfoDownloads / Week
Parent folder
SEDB75.zip 2019-11-28 123.9 MB
README.txt 2019-11-28 4.8 kB
Totals: 2 Items   123.9 MB 0
SEDB75 Release Databases
=========================

SEOW SEDB75 Release Notes 19 November 2019

This folder contains all SEOW database files needed to execute campaigns in any of the 96 supported databases of SEOW v7.3.0
The files are in MySQL format. Support for MSAccess database flavours has been discontinued due to lack of interest.

MySQL
-----
The files in this folder are variants of SEDB75 created in MySQL (.sql) format. Each database variant comes in
"MySQL_simple" and "MySQL_extended" formats. Some MySQL database administration tools may prefer the simple format, 
whilst others (e.g. Navicat) will work most happily with the extended format. 

The Reference SEDB75 MySQL database contains all 2.3 million records for all 96 sectors. This is intended to be a resource
for SEOW developers, and is not normally recommended for use as a production campaign database.

MySQL_simple/SEDB75_Reference.sql
MySQL_extended/SEDB75_Reference_extinserts.sql


"Lite" versions are also supplied for each sector. These contain only information relevant to the sector, thus giving improved 
efficiency for administration and query performance. For all the "Lite" versions, the individual databases can only support 
campaign operations in the relevant sector. The standard SQL "Lite" versions are:

MySQL_simple Folder
=================
SEDB75_Africa_NE.sql
SEDB75_Africa_NW.sql
SEDB75_Aleutians.sql
SEDB75_Ardennes.sql
SEDB75_Balaton.sql
SEDB75_BarentsSea.sql
SEDB75_BattleofKursk.sql
SEDB75_BattleofMoscow.sql
SEDB75_BayofBiscay.sql
SEDB75_Berlin.sql
SEDB75_Borneo.sql
SEDB75_Burma.sql
SEDB75_Cartagena.sql
SEDB75_CentralMed.sql
SEDB75_Channel1940.sql
SEDB75_Channel1942.sql
SEDB75_ChannelCircus.sql
SEDB75_CoralSea.sql
SEDB75_Crete.sql
SEDB75_Crimea.sql
SEDB75_Cyrenaica.sql
SEDB75_Darwin.sql
SEDB75_Donbass.sql
SEDB75_ElAlamein.sql
SEDB75_EnglishChannel.sql
SEDB75_FortressMalta.sql
SEDB75_GothicLine.sql
SEDB75_Guadalcanal.sql
SEDB75_GulfofFinland.sql
SEDB75_Hawaii.sql
SEDB75_Iasi.sql
SEDB75_IF_Baranow.sql
SEDB75_IF_Staszow.sql
SEDB75_Imphal.sql
SEDB75_Italy.sql
SEDB75_ItalyExp.sql
SEDB75_Italy_Africa_Greece.sql
SEDB75_Italy_Greece.sql
SEDB75_IwoJima.sql
SEDB75_KhalkhinGol.sql
SEDB75_KhalkhinGolExp.sql
SEDB75_Kiev.sql
SEDB75_Kiev_AP.sql
SEDB75_Korea.sql
SEDB75_Kuban.sql
SEDB75_Kurland.sql
SEDB75_Kursk.sql
SEDB75_Kyushu.sql
SEDB75_Libya.sql
SEDB75_Lvov.sql
SEDB75_Malta.sql
SEDB75_Manchuria.sql
SEDB75_Marianas.sql
SEDB75_MarianasExp.sql
SEDB75_Mediterranean.sql
SEDB75_Midway.sql
SEDB75_MidwayLarge.sql
SEDB75_Moscow.sql
SEDB75_Murmansk.sql
SEDB75_NewGuinea.sql
SEDB75_Normandy.sql
SEDB75_NorthSea.sql
SEDB75_Odessa.sql
SEDB75_Okinawa.sql
SEDB75_Oslo.sql
SEDB75_Ostfriesland.sql
SEDB75_Palau.sql
SEDB75_Palembang.sql
SEDB75_Philippines.sql
SEDB75_Prokhorovka.sql
SEDB75_Provence.sql
SEDB75_Sakishima.sql
SEDB75_SantaCruz.sql
SEDB75_Sardegna.sql
SEDB75_Sinai.sql
SEDB75_Singapore.sql
SEDB75_Slovakia.sql
SEDB75_Slovenia.sql
SEDB75_Smolensk.sql
SEDB75_Stalingrad.sql
SEDB75_StalingradWinter.sql
SEDB75_Tarawa.sql
SEDB75_Thailand.sql
SEDB75_TheFall.sql
SEDB75_TheSlotAug42.sql
SEDB75_TheSlotDec42.sql
SEDB75_TheSlotJan44.sql
SEDB75_TheSlotJul43.sql
SEDB75_TheSlotOct42.sql
SEDB75_TheSlotOct43.sql
SEDB75_Truk.sql
SEDB75_Tubruq.sql
SEDB75_Tunis.sql
SEDB75_WesternCarolines.sql
SEDB75_WestFront40.sql
SEDB75_WestFront44.sql

MySQL_extended Folder
===================
The "extended SQL insert" versions have "_extinserts.sql" as the filename endings.


UTF-8 Character Set Support
===========================

SEOW permits unit names to be customized in order to satisfy a wide range of campaign scenarios. This 
means that airforce, army, navy and rail unit names can be specified by the campaign designer, simply
by editing the Airforce_Units, Army_Units, Navy_Units and Railway_Units tables. The edits can include
extended character support as long as (i) the characters are supported by the UTF-8 character set, and
(ii) the characters are entered in escaped hex format, e.g. \u00f6 is the same as the German o-umlaut.

The file "UTF-8.txt" included in this release provides an exhaustive listing of available UTF-8 characters
and their hex and html representations. The SEOW Statistics tool contains logic sufficient to decode and 
display all the characters used in the default Airforce_Units table; the coded mapping logic is
are found in the LL() function defined in the Scripts/MP-SpecialCharacters.php file. If extra characters
are used anywhere in the database, then please ensure that the LL() function is brought up to date, 
otherwise corrupted display of relevant unit names is likely.

Enjoy!
IV/JG7_4Shades
28 November 2019
Source: README.txt, updated 2019-11-28