Redigerer MySQL (avsnitt)

== Eksempel ==

<pre>
Lage tabell: CREATE TABLE tabel navn
(
Navn på kolone data_type,
Navn på kolone2 data_type,
Navn på kolone3 data_type,
....
);

Legge til Infomasjon:
INSERT INTO tabel_navn (kolone1, kolone2, kolone3,...)
VALUES (info1, info2, info3,...)

Hente infomasjon:
SELECT * FROM tabel_navn (WHERE kolone1(ORDER BY kolone2 DESC(LIMIT 0, 10)))

Oppdatere infomasjon:
UPDATE tabel_navn
SET kolone1=info, kolone2=info2,...
WHERE en_kolone=en_info

Slette kolone:
DELETE FROM table_navn
WHERE en_kolone = en_info 
</pre>

Utfylling:
<pre>
Lage tabel: CREATE TABLE brukere
(
id int(9) NOT NULL AUTO_INCREMENT,
brukernavn varchar(255) NOT NULL,
passord varchar(255) NOT NULL,
....
);

Legge til Infomasjon:
INSERT INTO brukere (brukernavn, passord, email,...)
VALUES (Testern, *********, minepost@gmail.com,...)

Hente infomasjon:
SELECT * FROM brukere (WHERE id(ORDER BY id DESC(LIMIT 0, 10)))

Oppdatere infomasjon:
UPDATE brukere
SET brukernavn=Tewstern, passord=*****,...
WHERE id=2

Slette kolone:
DELETE FROM brukere
WHERE id = 2 (Resultatet vil bli at bruker id 2 vil bli slettet) 
</pre>
Der det står Hente infomasjon og i koden stod det <code>...e (WHERE id(ORDER BY id DESC(LIMIT 0, 10)))</code>.
Dette betyr at det som står inne parentes kan brukes.
<!-- Earlier versions of the MySQL manual included claims that certain essential missing features were useless or even harmful, and that users were better off without them. One section, entitled "Reasons NOT to use Foreign Keys constraints" (sic) advised users that relational-integrity checking was difficult to use and complicated a database application, and that its only useful purpose was to allow client software to diagram the relationships between database tables. [http://sunsite.univie.ac.at/textbooks/mysql/manual.html#Broken_Foreign_KEY] Another section claimed that a DBMS lacking transactions can provide as reliable of data-integrity assurances as one supporting them &mdash; conflating the issue of transactional integrity with that of saving data when the database server loses power. [http://sunsite.univie.ac.at/textbooks/mysql/manual.html#IDX340] Since these claims contradicted basic principles of [[relational database]] design, they caused MySQL to be ridiculed by some database experts. Right or wrong, these claims have since been removed in more recent versions of the manual. MySQL today supports the previously-dismissed features of relational integrity checking and transactions in an effort to meet the broadest needs, and facilitate migration efforts.

Critics find MySQL's popularity surprising in the light of the existence of other open-source database projects with comparable performance and in closer compliance to the SQL standards. MySQL advocates reply that the program serves its purpose for its users, who are willing to accept the program's limitations (which decrease with every major revision) in exchange for speed, simplicity, and rapid development.

Some users have also criticized MySQL AB's position on the licensing of the software. -->