Apa jenis model data mysql?

MySQL Workbench menyediakan kemampuan ekstensif untuk membuat dan memanipulasi model database. Beberapa kemampuan ini tercantum di sini

Ini bukan daftar yang lengkap. Ini, dan kemampuan pemodelan data tambahan, dibahas di bagian berikut

Layar Beranda adalah titik awal umum untuk bekerja dengan pemodelan data. Di bagian Pemodelan Data di Ruang Kerja, Anda dapat menggunakan item tindakan di sana untuk membuat dan mengelola model, merekayasa maju dan mundur, serta membandingkan dan menyinkronkan skemata. Item tindakan ini tercantum di bawah ini

7. 1. Buka Model EER yang Ada

Mengklik item tindakan ini meluncurkan browser file. Anda kemudian dapat memilih file model yang ingin Anda muat. Tab Model MySQL baru kemudian akan dibuat, dan model Anda ditampilkan

Buka Model EER yang Ada (ikon)

Jika Anda telah membuat satu atau lebih file model, Anda cukup mengklik dua kali item model yang ingin Anda muat. Tab Model MySQL baru akan dibuat, dan model Anda ditampilkan

Anda dapat membaca lebih lanjut tentang pemodelan di bagian ini

7. 2. Buat Model EER baru

Mengklik item tindakan ini akan meluncurkan tab Model MySQL baru, dengan model kosong yang siap untuk Anda kerjakan

Anda dapat membaca lebih lanjut tentang pemodelan di bagian ini

7. 3. Buat Model EER dari Database yang Ada

Tujuan item tindakan ini adalah untuk memungkinkan Anda membuat Model EER dari database langsung yang sudah ada. Mengklik item tindakan ini meluncurkan Reverse Engineer Database. Ini adalah wizard multi-tahap yang memungkinkan Anda memilih koneksi ke server langsung, dan memilih skema dan objek yang ingin Anda rekayasa ulang ke dalam model baru Anda. Ini adalah cara mudah untuk melihat bagaimana struktur database yang ada

Untuk informasi lebih lanjut tentang reverse engineering lihat

7. 4. Buat Model EER dari Skrip SQL

Tujuan dari item tindakan ini adalah untuk memungkinkan Anda membuat model dari skrip SQL Create. Skrip semacam itu mungkin dibuat dengan tangan atau mungkin sebagai hasil dari rekayasa balik database yang ada untuk menghasilkan skrip, yang kemudian dapat dimodifikasi sesuai dengan kebutuhan. Mengklik item tindakan ini meluncurkan wizard Reverse Engineer SQL Script. Ini adalah wizard multi-tahap yang memungkinkan Anda memilih skrip yang ingin Anda buat modelnya

Untuk informasi lebih lanjut lihat

Ketika Editor Model dijalankan dari Layar Beranda, halaman Model MySQL ditampilkan. Halaman Model MySQL memiliki tiga panel utama. Editor Deskripsi, panel Daftar/Riwayat Jenis Pengguna, dan panel utama - panel Ikhtisar Model. Editor Deskripsi dan panel Daftar/Riwayat Jenis Pengguna terdapat di dalam Bilah Samping. Bilah Samping terletak di sebelah kiri secara default, tetapi dapat dipindahkan ke kanan menggunakan pengaturan dalam dialog Preferensi Meja Kerja

Gambar 7. 1. Halaman

Total number of Schemata: {{SCHEMA_COUNT}}

Bagian dalam panel Model Overview adalah

• Diagram EER

• Skema Fisik

• Hak Istimewa Skema

• Skrip SQL

• Catatan Model

Untuk setiap objek bagian ini dapat ditambahkan ke proyek dengan mengklik ikon tambahkan objek yang sesuai. Anda juga dapat mengganti nama, mengedit, memotong, menyalin, atau menghapus objek di halaman ini dengan mengklik kanan. Melakukan ini akan membuka menu pop-up

Bagian dalam halaman Model MySQL dibahas di bagian berikut

Beberapa pilihan menu tidak tersedia di versi OSS aplikasi ini, dan hanya tersedia di Edisi Standar. Ini ditunjukkan jika berlaku

Opsi cetak hanya diaktifkan jika tab Diagram EER dipilih. Anda memiliki pilihan untuk mencetak model Anda langsung ke printer Anda, mencetaknya sebagai file PDF, atau membuat file PostScript. Untuk informasi lebih lanjut lihat

Opsi pencetakan hanya tersedia dalam versi komersial MySQL Workbench

• Total number of Schemata: {{SCHEMA_COUNT}}

  _6. Default ke

  Total number of Schemata: {{SCHEMA_COUNT}}

  5

• Total number of Schemata: {{SCHEMA_COUNT}}

  _8. Nomor versi proyek

• Total number of Schemata: {{SCHEMA_COUNT}}

  _9. Penulis proyek

• Total number of Schemata: 2

  0. Nama proyek

• Total number of Schemata: 2

  1. Tidak dapat diedit, ditentukan oleh atribut file MWB

• Total number of Schemata: 2

  2. Tidak dapat diedit, ditentukan oleh atribut file MWB

• Total number of Schemata: 2

  _3. Deskripsi proyek Anda

Jika halaman

Total number of Schemata: {{SCHEMA_COUNT}}

7. 5. 1. 2. 1. Temukan Jendela Dialog

Edisi Standar Meja Kerja MySQL menyertakan fasilitas Temukan yang lebih canggih

Gambar 7. 2. Jendela Temukan

Anda dapat mencari lokasi berikut

• Seluruh Model. Cari seluruh model

• Pandangan saat ini. Cari tampilan saat ini saja. Ini mungkin halaman

  Total number of Schemata: {{SCHEMA_COUNT}}

  5

• Semua Tampilan. Cari

  Total number of Schemata: 2

  _6 dan semua diagram EER

• Objek Basis Data. Cari objek basis data saja

• Angka Terpilih. Cari objek yang dipilih saat ini. Fitur ini hanya berfungsi untuk diagram EER

Masukkan teks yang ingin Anda cari di kotak daftar tarik-turun Temukan Teks. Anda juga dapat memilih salah satu atau semua kotak centang berikut

• Cocok Kasus

• Seluruh kata

• Gunakan Ekspresi Reguler

• Cari di Komentar

• Cari di SQL untuk Views, SPs dll

Teks apa pun yang Anda masukkan ke dalam kotak daftar drop-down Temukan Teks dipertahankan selama durasi sesi Anda. Gunakan tombol Berikutnya atau Sebelumnya untuk menemukan kemunculan kriteria pencarian Anda

Mengklik tombol Temukan Semua membuka jendela Temukan Hasil yang berlabuh di bagian bawah aplikasi. Jika Anda mau, Anda dapat melepaskan jendela ini seperti yang Anda lakukan pada jendela lainnya

Gunakan jendela ini untuk menavigasi ke objek. Misalnya, mengklik dua kali

Total number of Schemata: 2

Total number of Schemata: 2

Jendela dialog

Total number of Schemata: 2

Total number of Schemata: 2

7. 5. 1. 2. 2. Preferensi Meja Kerja

Opsi menu ini memungkinkan Anda mengatur preferensi global untuk aplikasi MySQL Workbench

Untuk informasi lebih lanjut lihat

Opsi yang tersedia di bawah item menu ini adalah

• Opsi menu ini menyediakan sarana untuk membuka jendela yang terkait dengan opsi ini

• Kemampuan untuk memperbesar diagram EER juga tersedia menggunakan alat penggeser di palet

  {{#SCHEMATA}}
  Schema: {{SCHEMA_NAME}}
  {{/SCHEMATA}}

  1. Lihat

7. 5. 1. 4. Menu Susun

Opsi menu

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Opsi menu yang tersedia di bawah item menu

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

• Tambahkan Diagram. Buat Diagram EER baru. Pintasan keyboard adalah Ctrl T

• Buat Diagram Dari Objek Katalog. Buat diagram EER dari semua objek di katalog

• DBDoc – Pelaporan Model. Untuk informasi tentang penggunaan opsi menu ini, lihat. Versi komersial saja

• Jenis yang Ditentukan Pengguna. Memilih opsi menu ini memberi Anda kotak dialog, memungkinkan Anda untuk menambah dan menghapus tipe data yang ditentukan pengguna

• Notasi Objek. Item yang tersedia di bawah opsi ini dibahas di

• Notasi Relasi. Item yang tersedia di bawah opsi ini dibahas di

• Properti Diagram dan Ukuran. Memilih opsi menu ini akan membuka kotak dialog ukuran diagram. Gunakan kotak dialog ini untuk menyesuaikan lebar atau tinggi kanvas. Satuan ukurannya adalah halaman;

  Saat Anda memiliki tabel dengan banyak kolom, gunakan opsi menu ini untuk menambah ukuran EER

• Validasi. Item yang tersedia di bawah opsi ini dibahas di. Versi komersial saja

• Opsi Model. Tetapkan opsi di tingkat model. Opsi ini tidak boleh disamakan dengan opsi yang ditetapkan secara global untuk aplikasi Workbench, dan yang sekarang disebut sebagai Preferensi Workbench. Opsi model yang tersedia adalah subset dari opsi Preferensi Meja Kerja

  Untuk informasi lebih lanjut tentang Preferensi Meja Kerja, lihat

7. 5. 1. 5. 1. Jendela Dialog Pelaporan Model DBDoc (Versi Komersial)

Gunakan jendela dialog ini untuk menyetel opsi untuk membuat dokumentasi model database Anda

Anda dapat tentang item menu ini secara lebih rinci di bagian berikut

7. 5. 1. 5. 3. Opsi Menu Notasi Objek

Pilihan menunya adalah sebagai berikut

Gaya notasi objek yang Anda pilih tetap ada selama sesi MySQL Workbench Anda dan disimpan bersama dengan model Anda. Saat MySQL Workbench dimulai ulang, notasi objek kembali ke default

Jika Anda berencana untuk mengekspor atau mencetak diagram EER, pastikan untuk menentukan gaya notasi terlebih dahulu. Mengubah gaya notasi setelah objek ditempatkan pada diagram dapat mengubah tampilan diagram secara signifikan

7. 5. 1. 5. 4. Opsi Menu Notasi Relasi

Untuk melihat gaya yang berbeda, atur hubungan antara dua tabel atau lebih dan pilih opsi menu yang berbeda

Gaya notasi hubungan yang Anda pilih tetap ada selama sesi MySQL Workbench Anda dan disimpan bersama dengan model Anda. Saat MySQL Workbench dimulai ulang, notasi hubungan kembali ke default, gaya

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Jika Anda berencana untuk mengekspor atau mencetak diagram EER, pastikan untuk menentukan gaya notasi terlebih dahulu. Mengubah gaya notasi setelah objek ditempatkan pada diagram dapat mengubah tampilan diagram secara signifikan

7. 5. 1. 6. Menu Basis Data

7. 5. 1. 7. Menu Plugin

7. 5. 1. 8. Menu Skrip

Menu ini saat ini memiliki tiga item

7. 5. 1. 9. Menu Komunitas

Gunakan opsi menu ini untuk online dan mempelajari lebih lanjut tentang MySQL Workbench

Gunakan opsi menu ini untuk online dan mempelajari lebih lanjut tentang MySQL Workbench

read_mysql_cfg_file  C:\Program Files\MySQL\MySQL Server 5.1\my.ini
[('tmp_table_size', '9M'), 
('myisam_sort_buffer_size', '18M'), 
('table_cache', '256'), 
('read_rnd_buffer_size', '256K'), 
('port', '3306'), ('max_connections', '100'), 
('innodb_buffer_pool_size', '18M'), 
('myisam_max_sort_file_size', '100G'), 
('sql-mode', '"STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"'), 
('basedir', '"C:/Program Files/MySQL/MySQL Server 5.1/"'), 
('default-character-set', 'latin1'), 
('datadir', '"C:/ProgramData/MySQL/MySQL Server 5.1/Data/"'), 
('innodb_log_buffer_size', '1M'), 
('innodb_log_file_size', '10M'), 
('innodb_thread_concurrency', '8'), 
('read_buffer_size', '64K'), 
('innodb_additional_mem_pool_size', '2M'), 
('thread_cache_size', '8'), 
('innodb_flush_log_at_trx_commit', '1'), 
('query_cache_size', '0'), 
('sort_buffer_size', '256K'), 
('default-storage-engine', 'INNODB'), 
('key_buffer_size', '11M')]
MySQL Workbench OSS for Windows version 5.2.8
Cairo Version: 1.8.6
Rendering Mode: GDI requested (create a diagram to confirm)
OpenGL Driver Version: Not Detected
OS: unknown
CPU: Intel(R) Core(TM)2 Duo CPU     T9300  @ 2.50GHz, 1.0 GB RAM
Video adapter info:
Adapter type: VirtualBox Graphics Adapter
Chip Type: VBOX
BIOS String: Version 0xB0C2 or later
Video Memory: 12288 KB

Bilah alat MySQL Workbench ditemukan tepat di bawah bilah menu. Alat berikut selalu muncul di bilah alat

• Ikon dokumen baru. Klik ikon ini untuk membuat dokumen baru

• Ikon folder. Klik ikon ini untuk membuka file MySQL Workbench (MWB)

• Ikon simpan. Klik ikon ini untuk menyimpan proyek MySQL Workbench saat ini

• Panah kanan dan kiri. Klik panah kiri untuk melakukan operasi "Undo". Klik panah kanan untuk melakukan operasi "Redo".

Alat lain muncul di bilah alat tergantung pada konteksnya

Saat kanvas diagram EER dipilih, ikon berikut muncul di sebelah kanan ikon panah

• Ikon kotak beralih. Digunakan untuk menghidupkan dan mematikan jaringan

• Ikon kisi. Digunakan untuk menyelaraskan objek di kanvas dengan kisi

7. 5. 2. 1. Item Toolbar khusus alat

Bilah alat juga berubah tergantung alat mana dari bilah alat vertikal yang aktif. Alat-alat ini dibahas di

Jika alat

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Saat objek dipilih, properti objek, seperti warna, dapat diubah di Editor Properti

Gunakan ikon

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

7. 5. 4. Skema Fisik

Panel

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Total number of Schemata: {{SCHEMA_COUNT}}

Luaskan dan kontraksikan bagian

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Setiap skema ditampilkan sebagai tab; . Saat MySQL Workbench pertama kali membuka skema default,

Schema: Airlines
Schema: Airports

Ada berbagai cara untuk menambahkan skema ke panel

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Anda juga dapat menambahkan skema baru dengan mengeklik tombol + di kanan atas panel

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Panel

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

• Tabel

• Tampilan

• Rutinitas

• Grup Rutin

Setiap bagian berisi objek database yang ditentukan dan ikon yang digunakan untuk membuat objek tambahan

Setiap objek database yang ditambahkan ke kanvas diagram EER juga muncul di bagian

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Panel

Schema: Airlines
Schema: Airports

Total number of Schemata: {{SCHEMA_COUNT}}

Panel

Schema: Airlines
Schema: Airports

Gambar berikut menampilkan bagian

Schema: Airlines
Schema: Airports

Total number of Schemata: {{SCHEMA_COUNT}}

Gambar 7. 3. Peran dan Keistimewaan

Untuk menambahkan peran, klik dua kali ikon

    Report
    ------
    Column Name: {{COLUMN_NAME}}
  

    Report
    ------
    Column Name: {{COLUMN_NAME}}
  

Untuk mengganti nama peran, cukup klik nama peran dan Anda kemudian dapat mengedit teksnya

Semua peran yang telah ditentukan tercantum di bawah

    Report
    ------
    Column Name: {{COLUMN_NAME}}
  

Gambar 7. 4. Editor Peran

Pilih peran yang ingin Anda tambahkan objek. Anda dapat menarik dan melepas objek dari

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

    Report
    ------
    Column Name: {{COLUMN_NAME}}
  

    Report
    ------
    Column Name: {{COLUMN_NAME}}
  

    Report
    ------
    Column Name: {{COLUMN_NAME}}
  

Schema: Airlines
Schema: Airports

    Report
    ------
    {{#COLUMNS}}
    Column Name: {{COLUMN_NAME}}
    {{/COLUMNS}}
  

    Report
    ------
    {{#COLUMNS}}
    Column Name: {{COLUMN_NAME}}
    {{/COLUMNS}}
  

Untuk menambahkan pengguna, klik dua kali ikon

    Report
    ------
    {{#COLUMNS}}
    Column Name: {{COLUMN_NAME}}
    {{/COLUMNS}}
  

    Report
    ------
    {{#COLUMNS}}
    Column Name: {{COLUMN_NAME}}
    {{/COLUMNS}}
  

Di

    Report
    ------
    {{#COLUMNS}}
    Column Name: {{COLUMN_NAME}}
    {{/COLUMNS}}
  

Mengklik kanan pengguna membuka menu pop-up. Opsi ini berfungsi seperti yang dijelaskan di

7. 5. 6. Skrip SQL dan Catatan Model

Dua panel yang tersisa pada halaman

Total number of Schemata: {{SCHEMA_COUNT}}

    Report
    ------
    {{#COLUMNS}}
    Column Name: {{COLUMN_NAME}}
    {{/COLUMNS}}
  

    Report
    ------
    {{#COLUMNS}}
    Column Name: {{COLUMN_NAME}}
    {{/COLUMNS}}
  

Gunakan panel

    Report
    ------
    {{#COLUMNS}}
    Column Name: {{COLUMN_NAME}}
    {{/COLUMNS}}
  

    Report
    ------
    {{#COLUMNS}}
    Column Name: {{COLUMN_NAME}}
    {{/COLUMNS}}
  

    Report
    ------
    {{#COLUMNS}}
    Column Name: {{COLUMN_NAME}}
    {{/COLUMNS}}
  

Gunakan panel

    Report
    ------
    {{#COLUMNS}}
    Column Name: {{COLUMN_NAME}}
    {{/COLUMNS}}
  

7. 5. 7. Palet Sejarah

Hanya tindakan yang mengubah model MySQL atau mengubah diagram EER yang ditangkap oleh palet

    Report
    ------

    {{#SCHEMATA}}
    {{#TABLES}}
    {{#COLUMNS_LISTING}}
    {{#COLUMNS}}
    Column Name: {{COLUMN_NAME}}
    {{/COLUMNS}}
    {{/COLUMNS_LISTING}}
    {{/TABLES}}
    {{/SCHEMATA}}

  

7. 5. 8. Panel Navigator Model

Berlabuh di kiri atas aplikasi adalah Model Navigator, atau panel Bird's Eye. Panel ini memberi Anda ikhtisar objek yang ditempatkan pada kanvas diagram EER dan karena alasan ini sangat berguna saat diagram EER aktif. Objek apa pun yang telah Anda tempatkan di kanvas harus terlihat di navigator

Model Navigator menunjukkan luas total diagram EER. Garis persegi panjang hitam menunjukkan area pandang ke area kanvas yang terlihat. Untuk mengubah port tampilan diagram EER klik kiri garis hitam ini dan seret ke lokasi yang diinginkan. Anda dapat memperbesar area tertentu dari diagram EER dengan menggunakan alat penggeser di bagian bawah jendela ini. Dimensi port tampilan berubah saat Anda memperbesar dan memperkecil. Jika alat penggeser memiliki fokus, Anda juga dapat memperbesar menggunakan tombol panah

Gambar 7. 5. Palet Navigator Model

7. 5. 9. Palet Pohon Katalog

Palet

    Report
    ------

    {{#SCHEMATA}}
    {{#TABLES}}
    {{#COLUMNS_LISTING}}
    {{#COLUMNS}}
    Column Name: {{COLUMN_NAME}}
    {{/COLUMNS}}
    {{/COLUMNS_LISTING}}
    {{/TABLES}}
    {{/SCHEMATA}}

  

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Total number of Schemata: {{SCHEMA_COUNT}}

• Tabel

• Tampilan

• Grup Rutin

Perluas masing-masing secara bergantian dengan mengklik tombol + di sebelah kiri ikon folder

Memilih objek dalam palet ini, menampilkan propertinya di palet

Total number of Schemata: 2

Palet Pohon Katalog terutama digunakan untuk menarik dan melepaskan objek ke kanvas diagram EER

Di Linux, ada kekhasan dalam kontrol pohon GTK, di mana klik sederhana selalu menghasilkan pilihan baru. Jika Anda ingin menyeret beberapa objek dari Pohon Katalog ke kanvas diagram EER, Anda perlu melakukan operasi sebagai berikut

1. Klik item pertama di pohon

2. Tahan shift dan klik item terakhir dan jangan lepaskan tombol shift

3. Tekan terus tombol shift dan mulai operasi penarikan

4. Lepaskan tombol shift sebelum Anda melepaskan tombol mouse untuk berhasil menjatuhkan objek yang dipilih ke kanvas

Ini juga berlaku untuk penggunaan tombol Ctrl saat memilih beberapa elemen yang tidak berdekatan di Pohon Katalog

Anda dapat mengaktifkan dan menonaktifkan sidebar menggunakan tombol Toggle Sidebar, yang terletak di kanan atas aplikasi

7. 5. 10. Palet Lapisan

Memilih objek di palet

    Report
    ------

    {{#SCHEMATA}}
    {{#TABLES}}
    {{#COLUMNS_LISTING}}
    {{#COLUMNS}}
    Column Name: {{COLUMN_NAME}}
    {{/COLUMNS}}
    {{/COLUMNS_LISTING}}
    {{/TABLES}}
    {{/SCHEMATA}}

  

7. 5. 10. 1. Menemukan Objek Tak Terlihat Menggunakan Palet Lapisan

Dalam beberapa keadaan, Anda mungkin ingin membuat objek pada diagram EER tidak terlihat. Untuk melakukan ini, pilih objek dan, di palet

Total number of Schemata: 2

    Report
    ------

    {{#SCHEMATA}}
    {{#TABLES}}
    {{#COLUMNS_LISTING}}
    {{#COLUMNS}}
    Column Name: {{COLUMN_NAME}}
    {{/COLUMNS}}
    {{/COLUMNS_LISTING}}
    {{/TABLES}}
    {{/SCHEMATA}}

  

    Report
    ------

    {{! Main dictionary active}}
    {{#SCHEMATA}}  {{! SCHEMATA dictionary active}}
    {{#TABLES}}  {{! TABLES dictionary active}}
    {{#COLUMNS_LISTING}} {{! COLUMNS_LISTING dictionary active}}
    {{#COLUMNS}}  {{! COLUMNS dictionary active}}
    Column Name: {{COLUMN_NAME}} {{! COLUMN_NAME variable is looked-up, and found, in COLUMNS data dictionary}}
    {{/COLUMNS}}
    {{/COLUMNS_LISTING}}
    {{/TABLES}}
    {{/SCHEMATA}}

  

Palet

    Report
    ------

    {{! Main dictionary active}}
    {{#SCHEMATA}}  {{! SCHEMATA dictionary active}}
    {{#TABLES}}  {{! TABLES dictionary active}}
    {{#COLUMNS_LISTING}} {{! COLUMNS_LISTING dictionary active}}
    {{#COLUMNS}}  {{! COLUMNS dictionary active}}
    Column Name: {{COLUMN_NAME}} {{! COLUMN_NAME variable is looked-up, and found, in COLUMNS data dictionary}}
    {{/COLUMNS}}
    {{/COLUMNS_LISTING}}
    {{/TABLES}}
    {{/SCHEMATA}}

  

    Report
    ------

    {{! Main dictionary active}}
    {{#SCHEMATA}}  {{! SCHEMATA dictionary active}}
    {{#TABLES}}  {{! TABLES dictionary active}}
    {{#COLUMNS_LISTING}} {{! COLUMNS_LISTING dictionary active}}
    {{#COLUMNS}}  {{! COLUMNS dictionary active}}
    Column Name: {{COLUMN_NAME}} {{! COLUMN_NAME variable is looked-up, and found, in COLUMNS data dictionary}}
    {{/COLUMNS}}
    {{/COLUMNS_LISTING}}
    {{/TABLES}}
    {{/SCHEMATA}}

  

    Report
    ------

    {{#SCHEMATA}}
    {{#TABLES}}
    {{#COLUMNS_LISTING}}
    {{#COLUMNS}}
    Column Name: {{COLUMN_NAME}}
    {{/COLUMNS}}
    {{/COLUMNS_LISTING}}
    {{/TABLES}}
    {{/SCHEMATA}}

  

    Report
    ------

    {{! Main dictionary active}}
    {{#SCHEMATA}}  {{! SCHEMATA dictionary active}}
    {{#TABLES}}  {{! TABLES dictionary active}}
    {{#COLUMNS_LISTING}} {{! COLUMNS_LISTING dictionary active}}
    {{#COLUMNS}}  {{! COLUMNS dictionary active}}
    Column Name: {{COLUMN_NAME}} {{! COLUMN_NAME variable is looked-up, and found, in COLUMNS data dictionary}}
    {{/COLUMNS}}
    {{/COLUMNS_LISTING}}
    {{/TABLES}}
    {{/SCHEMATA}}

  

7. 5. 11. Palet Properti

Palet

Total number of Schemata: 2

Semua objek kecuali koneksi memiliki properti berikut kecuali seperti yang disebutkan

•     Report
      ------
  
      {{! Main dictionary active}}
      {{#SCHEMATA}}  {{! SCHEMATA dictionary active}}
      {{#TABLES}}  {{! TABLES dictionary active}}
      {{#COLUMNS_LISTING}} {{! COLUMNS_LISTING dictionary active}}
      {{#COLUMNS}}  {{! COLUMNS dictionary active}}
      Column Name: {{COLUMN_NAME}} {{! COLUMN_NAME variable is looked-up, and found, in COLUMNS data dictionary}}
      {{/COLUMNS}}
      {{/COLUMNS_LISTING}}
      {{/TABLES}}
      {{/SCHEMATA}}
  
    

  _6. Aksen warna objek. Warna objek ditampilkan di sini seperti nilai heksadesimalnya. Ubah warna objek dengan mengubah nilai ini. Only characters that are legal for hexadecimal values may be entered. You can also change the color by clicking the . button. This opens a color changer dialog box

•     Report
      ------
  
      {{! Main dictionary active}}
      {{#SCHEMATA}}  {{! SCHEMATA dictionary active}}
      {{#TABLES}}  {{! TABLES dictionary active}}
      {{#COLUMNS_LISTING}} {{! COLUMNS_LISTING dictionary active}}
      {{#COLUMNS}}  {{! COLUMNS dictionary active}}
      Column Name: {{COLUMN_NAME}} {{! COLUMN_NAME variable is looked-up, and found, in COLUMNS data dictionary}}
      {{/COLUMNS}}
      {{/COLUMNS_LISTING}}
      {{/TABLES}}
      {{/SCHEMATA}}
  
    

  7. Applicable to layers only. A means of documenting the purpose of a layer

•     Report
      ------
  
      {{! Main dictionary active}}
      {{#SCHEMATA}}  {{! SCHEMATA dictionary active}}
      {{#TABLES}}  {{! TABLES dictionary active}}
      {{#COLUMNS_LISTING}} {{! COLUMNS_LISTING dictionary active}}
      {{#COLUMNS}}  {{! COLUMNS dictionary active}}
      Column Name: {{COLUMN_NAME}} {{! COLUMN_NAME variable is looked-up, and found, in COLUMNS data dictionary}}
      {{/COLUMNS}}
      {{/COLUMNS_LISTING}}
      {{/TABLES}}
      {{/SCHEMATA}}
  
    

  8. This attribute applies to objects such as tables that can be expanded to show columns, indexes, and triggers

•     Report
      ------
  
      {{! Main dictionary active}}
      {{#SCHEMATA}}  {{! SCHEMATA dictionary active}}
      {{#TABLES}}  {{! TABLES dictionary active}}
      {{#COLUMNS_LISTING}} {{! COLUMNS_LISTING dictionary active}}
      {{#COLUMNS}}  {{! COLUMNS dictionary active}}
      Column Name: {{COLUMN_NAME}} {{! COLUMN_NAME variable is looked-up, and found, in COLUMNS data dictionary}}
      {{/COLUMNS}}
      {{/COLUMNS_LISTING}}
      {{/TABLES}}
      {{/SCHEMATA}}
  
    

  9. The height of the object. Depending upon the object, this property may be read only or read/write

•     Report
      ------
  
      {{#SCHEMATA}}
      {{#TABLES}}
      {{#COLUMNS_LISTING}}
      {{#COLUMNS}}
      Schema Name: {{SCHEMA_NAME}} Column Name: {{COLUMN_NAME}}
      {{/COLUMNS}}
      {{/COLUMNS_LISTING}}
      {{/TABLES}}
      {{/SCHEMATA}}
  
    

  0. The number of pixels from the object to the left side of the canvas

•     Report
      ------
  
      {{#SCHEMATA}}
      {{#TABLES}}
      {{#COLUMNS_LISTING}}
      {{#COLUMNS}}
      Schema Name: {{SCHEMA_NAME}} Column Name: {{COLUMN_NAME}}
      {{/COLUMNS}}
      {{/COLUMNS_LISTING}}
      {{/TABLES}}
      {{/SCHEMATA}}
  
    

  1. Whether the object is locked or not. The value for this attribute is either

      Report
      ------
  
      {{#SCHEMATA}}
      {{#TABLES}}
      {{#COLUMNS_LISTING}}
      {{#COLUMNS}}
      Schema Name: {{SCHEMA_NAME}} Column Name: {{COLUMN_NAME}}
      {{/COLUMNS}}
      {{/COLUMNS_LISTING}}
      {{/TABLES}}
      {{/SCHEMATA}}
  
    

  2 or

      Report
      ------
  
      {{#SCHEMATA}}
      {{#TABLES}}
      {{#COLUMNS_LISTING}}
      {{#COLUMNS}}
      Schema Name: {{SCHEMA_NAME}} Column Name: {{COLUMN_NAME}}
      {{/COLUMNS}}
      {{/COLUMNS_LISTING}}
      {{/TABLES}}
      {{/SCHEMATA}}
  
    

  3

•     Report
      ------
  
      {{#SCHEMATA}}
      {{#TABLES}}
      {{#COLUMNS_LISTING}}
      {{#COLUMNS}}
      Schema Name: {{SCHEMA_NAME}} Column Name: {{COLUMN_NAME}}
      {{/COLUMNS}}
      {{/COLUMNS_LISTING}}
      {{/TABLES}}
      {{/SCHEMATA}}
  
    

  4. Whether the object has been manually sized or not. The value for this attribute is either

      Report
      ------
  
      {{#SCHEMATA}}
      {{#TABLES}}
      {{#COLUMNS_LISTING}}
      {{#COLUMNS}}
      Schema Name: {{SCHEMA_NAME}} Column Name: {{COLUMN_NAME}}
      {{/COLUMNS}}
      {{/COLUMNS_LISTING}}
      {{/TABLES}}
      {{/SCHEMATA}}
  
    

  2 or

      Report
      ------
  
      {{#SCHEMATA}}
      {{#TABLES}}
      {{#COLUMNS_LISTING}}
      {{#COLUMNS}}
      Schema Name: {{SCHEMA_NAME}} Column Name: {{COLUMN_NAME}}
      {{/COLUMNS}}
      {{/COLUMNS_LISTING}}
      {{/TABLES}}
      {{/SCHEMATA}}
  
    

  3

•     Report
      ------
  
      {{#SCHEMATA}}
      {{#TABLES}}
      {{#COLUMNS_LISTING}}
      {{#COLUMNS}}
      Schema Name: {{SCHEMA_NAME}} Column Name: {{COLUMN_NAME}}
      {{/COLUMNS}}
      {{/COLUMNS_LISTING}}
      {{/TABLES}}
      {{/SCHEMATA}}
  
    

  7. The name of the object

•     Report
      ------
  
      {{#SCHEMATA}}
      {{#TABLES}}
      {{#COLUMNS_LISTING}}
      {{#COLUMNS}}
      Schema Name: {{SCHEMA_NAME}} Column Name: {{COLUMN_NAME}}
      {{/COLUMNS}}
      {{/COLUMNS_LISTING}}
      {{/TABLES}}
      {{/SCHEMATA}}
  
    

  8. The number of pixels from the object to the top of the canvas

•     Report
      ------
  
      {{#SCHEMATA}}
      {{#TABLES}}
      {{#COLUMNS_LISTING}}
      {{#COLUMNS}}
      Column Name: {{COLUMN_NAME}}
      {{/COLUMNS}}
      {{/COLUMNS_LISTING}}
      {{/TABLES}}
      {{/SCHEMATA}}
  
    

  9. This property controls whether an object shows up on the canvas or not. Use

  Total number of Schemata: {{SCHEMA_COUNT}}

  00 for true and

  Total number of Schemata: {{SCHEMA_COUNT}}

  01 for false. It is currently only used for relationships

• Total number of Schemata: {{SCHEMA_COUNT}}

  02. The width of the object. Bergantung pada objeknya, properti ini mungkin hanya baca atau baca/tulis

Selain properti yang tercantum di atas, tabel juga memiliki properti berikut

• Total number of Schemata: {{SCHEMA_COUNT}}

  _03. Properti ini menentukan apakah indeks ditampilkan saat tabel ditempatkan di kanvas. Gunakan

  Total number of Schemata: {{SCHEMA_COUNT}}

  _00 untuk benar dan

  Total number of Schemata: {{SCHEMA_COUNT}}

  01 untuk salah

• Total number of Schemata: {{SCHEMA_COUNT}}

  _06. Properti ini menentukan apakah pemicu ditampilkan saat tabel ditempatkan di kanvas. Gunakan

  Total number of Schemata: {{SCHEMA_COUNT}}

  _00 untuk benar dan

  Total number of Schemata: {{SCHEMA_COUNT}}

  01 untuk salah

Untuk diskusi tentang sifat-sifat koneksi, lihat

Diagram EER dibuat dengan mengklik dua kali ikon

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Mengklik tab diagram EER menavigasi ke kanvas yang digunakan untuk memanipulasi objek database secara grafis. Di sisi kiri halaman ini adalah

Total number of Schemata: {{SCHEMA_COUNT}}

7. 6. 1. Bilah Alat Vertikal

Bilah alat vertikal muncul di bilah sisi kiri saat tab diagram EER dipilih. Alat pada bilah alat ini membantu membuat diagram EER

Gambar 7. 6. Bilah Alat Vertikal

Mengklik alat akan mengubah penunjuk tetikus menjadi penunjuk yang menyerupai ikon alat, yang menunjukkan alat mana yang aktif. Alat ini juga dapat diaktifkan dari keyboard dengan menekan tombol yang terkait dengan alat tersebut. Menempatkan mouse di atas ikon bilah alat menampilkan deskripsi alat dan tombol pintasannya

Penjelasan lebih rinci dari masing-masing alat berikut

7. 6. 1. 1. Penunjuk Mouse Standar

Penunjuk tetikus standar, yang terletak di bagian atas toolbar vertikal, adalah penunjuk tetikus default untuk sistem operasi Anda. Gunakan alat ini untuk kembali ke pointer mouse standar setelah menggunakan alat lain

Dari keyboard, gunakan tombol Esc untuk kembali ke penunjuk default

Alat tangan digunakan untuk memindahkan seluruh diagram EER. Klik kiri pada alat ini dan kemudian klik kiri di mana saja pada kanvas diagram EER sambil menahan tombol mouse. Memindahkan mouse mengubah port tampilan kanvas

Dari keyboard, gunakan tombol H untuk mengaktifkan alat ini

Anda juga dapat mengubah area pandang diagram ER menggunakan panel

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Gunakan alat penghapus untuk menghapus objek dari kanvas EER Diagram

Ubah penunjuk tetikus ke alat penghapus dan klik objek yang ingin Anda hapus. Bergantung pada pengaturan Anda, kotak dialog hapus akan terbuka, meminta Anda untuk mengonfirmasi jenis penghapusan

Tindakan penghapusan alat

Total number of Schemata: {{SCHEMA_COUNT}}

Dari keyboard, gunakan tombol D untuk mengaktifkan alat ini

Alat lapisan adalah ikon persegi panjang dengan huruf kapital

Total number of Schemata: {{SCHEMA_COUNT}}

Alat lapisan digunakan untuk mengatur objek pada kanvas EER Diagram. Ini berguna untuk mengelompokkan objek yang serupa. Anda dapat, misalnya, menggunakannya untuk mengelompokkan semua tampilan Anda

Klik alat lapisan dan gunakan untuk menggambar persegi panjang di kanvas. Ubah ke alat penunjuk mouse standar dan ambil objek apa pun yang ingin Anda tempatkan di lapisan yang baru dibuat

Untuk mengubah ukuran layer, pertama pilih dengan mengkliknya. Saat layer dipilih, persegi panjang kecil muncul di setiap sudut dan di tengah setiap sisi. Sesuaikan ukurannya dengan menyeret salah satu dari persegi panjang ini

Anda juga dapat membuat perubahan pada layer dengan memilih layer dan mengubah properti di panel Properties. Menggunakan panel Properties adalah satu-satunya cara untuk mengubah nama layer

Dari keyboard, gunakan tombol L untuk mengaktifkan alat ini. Untuk informasi lebih lanjut tentang lapisan, lihat

Alat teks adalah ikon persegi dengan huruf kapital

Total number of Schemata: {{SCHEMA_COUNT}}

Anda dapat memanipulasi properti objek teks dengan memilihnya lalu mengubah propertinya di panel

Total number of Schemata: 2

Dari keyboard, gunakan tombol N untuk mengaktifkan alat ini. Untuk informasi lebih lanjut tentang objek teks lihat

Gunakan alat gambar untuk menempatkan gambar di kanvas. Saat alat ini dipilih dan Anda mengklik kanvas, kotak dialog terbuka memungkinkan Anda memilih file grafik yang diinginkan

Dari keyboard, gunakan tombol I untuk mengaktifkan alat ini. For more information about images see

Gunakan alat ini untuk membuat tabel di kanvas EER Diagram

From the keyboard, use the T key to activate this tool

Untuk informasi selengkapnya tentang membuat dan mengedit tabel, lihat

Gunakan alat ini untuk membuat tampilan pada kanvas EER Diagram

Saat alat ini diaktifkan, kotak tarik-turun skema muncul di bilah alat di bawah menu utama, memungkinkan Anda mengaitkan tampilan baru dengan skema tertentu. Anda juga dapat memilih warna untuk objek dengan memilih dari kotak daftar tarik-turun warna di sebelah kanan kotak daftar skema

Dari keyboard, gunakan tombol V untuk mengaktifkan alat ini

For more information about creating and editing views see

7. 6. 1. 9. Alat Grup Rutin

Gunakan alat ini untuk membuat grup rutin di kanvas EER Diagram

When this tool is activated, a schema drop-down box appears on the toolbar below the main menu, allowing you to associate the routine group with a specific schema. Anda juga dapat memilih warna untuk grup rutin dengan memilih dari kotak daftar tarik-turun warna di sebelah kanan kotak daftar skema

From the keyboard, use the G key to activate this tool

For more information about creating and editing routine groups see

7. 6. 1. 10. The Relationship Tools

The five relationship tools are used to represent the following relationships

• Hubungan nonidentifying satu-ke-banyak

• Hubungan nonidentifikasi satu-ke-satu

• One-to-many identifying relationships

• Hubungan identifikasi satu-ke-satu

• Many-to-many identifying relationships

These tools appear at the bottom of the vertical tool bar. Mouse over each tool to see a text hint that describes its function

For more information about relationships see

7. 7. 1. 1. Adding Tables to the Physical Schemata

Double-clicking the

Total number of Schemata: {{SCHEMA_COUNT}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Total number of Schemata: {{SCHEMA_COUNT}}

Total number of Schemata: {{SCHEMA_COUNT}}

Total number of Schemata: {{SCHEMA_COUNT}}

Adding a new table automatically opens the table editor docked at the bottom of the application. Using the table editor is described in

Right-clicking a table opens a pop-up menu with the following options

The cut and copy options are useful for copying tables between different schemata

Any tables added to the

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Total number of Schemata: {{SCHEMA_COUNT}}

7. 7. 1. 2. Adding Tables to an EER Diagram

Tables can also be added to an EER Diagram using the

Total number of Schemata: {{SCHEMA_COUNT}}

Total number of Schemata: {{SCHEMA_COUNT}}

Clicking the mouse on this icon changes the mouse pointer to a table pointer. You can also change the mouse pointer to a table pointer by pressing the T key

Choosing the

Total number of Schemata: {{SCHEMA_COUNT}}

Total number of Schemata: {{SCHEMA_COUNT}}

Total number of Schemata: 2

Total number of Schemata: {{SCHEMA_COUNT}}

Total number of Schemata: {{SCHEMA_COUNT}}

Create a table by clicking anywhere on the EER Diagram canvas. Doing this creates a new table with the default name

Total number of Schemata: {{SCHEMA_COUNT}}

Figure 7. 7. A Table on an EER Diagram

As shown in the preceding diagram the primary key is indicated by a key icon and indexed fields are indicated by a different colored diamond icon. Click the arrow to the right of the table name to toggle the display of the fields. Alihkan tampilan indeks dan pemicu dengan cara yang sama

Right-clicking a table opens a pop-up menu with the following options

With the exception of the deletion option, these menu options function as described in . The behavior of the delete option is determined by your MySQL Workbench options settings. For more information, see

7. 7. 1. 3. The MySQL Table Editor

The MySQL Table Editor is a component that enables the creation and modification of tables. Using the MySQL Table Editor you can add or modify a table's columns or indexes, change the engine, add foreign keys, or simply alter the table's name

The MySQL Table Editor can be accessed from the MySQL Workbench by first selecting the MySQL Model tab and then double clicking a table in the

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

7. 7. 1. 3. 1. The Main Editor Window

Any number of tables may be edited in the MySQL Table Editor at any one time. Adding another table creates a new tab at the top of the editor. By default the MySQL Table Editor appears docked at the bottom of the application

The MySQL Table Editor is shown in the following figure

Figure 7. 8. The Table Editor

The MySQL Table Editor consists of a work space divided into the following tabs

• Table. Use this table to edit features that apply to the table as a whole

• Columns. Use this tab to add or modify columns

• Indexes. Use this tab to add or modify indexes

• Foreign Keys. Use this tab to add or modify foreign keys

• Triggers. Use this tab to add or modify triggers

• Partitioning. Use this tab to manage partitioning

• Options. Use this tab to add or modify various general, table and row level options

• Inserts. Use this tab for writing INSERT statements

• Privileges. Use this tab to set privileges on the table

Each of these tabs is discussed in further detail in the following sections

Use this tab to edit the table name or add a comment to the table. Easily change the collation or the table engine using drop down list boxes

7. 7. 1. 3. 3. The Columns Tab

The

Total number of Schemata: {{SCHEMA_COUNT}}

You can also use the column tab to change the name, data type, default value, and other properties of your table's columns

Figure 7. 9. The Columns Tab

To add a column simply click the

Total number of Schemata: {{SCHEMA_COUNT}}

• PK. Primary key

• NN. Not null

• UQ. Unique

• BIN. Biner

• PBB. Tidak ditandatangani

• ZF. Isi nol

• AI. Penambahan otomatis

Right-clicking a row under the

Total number of Schemata: {{SCHEMA_COUNT}}

To change the name, data type, default value, or comment of a column, double-click the value you wish to change. Konten kemudian menjadi dapat diedit

Anda juga dapat menambahkan komentar kolom ke area teks ________0______35. It is also possible to set the column collation, using the listbox in the Column Details panel

To the left of the column name is an icon that indicates whether the column is a member of the primary key. If the icon is a small key, that column belongs to the primary key, otherwise the icon is a blue diamond or a white diamond. Berlian biru menunjukkan kolom memiliki NN yang disetel. To add or remove a column from the primary key, double-click the icon. Anda juga dapat menambahkan kunci utama dengan mencentang kotak

Total number of Schemata: {{SCHEMA_COUNT}}

Total number of Schemata: {{SCHEMA_COUNT}}

Jika Anda ingin membuat kunci utama gabungan, Anda dapat memilih beberapa kolom dan mencentang kotak centang PK. Namun, ada langkah tambahan yang diperlukan, Anda harus mengklik tab Indeks, lalu di panel Kolom Indeks Anda perlu mengatur urutan kunci utama yang diinginkan

Saat memasukkan nilai default, dalam kasus

Total number of Schemata: {{SCHEMA_COUNT}}

Total number of Schemata: {{SCHEMA_COUNT}}

Harus berhati-hati saat memasukkan nilai default untuk kolom

Total number of Schemata: {{SCHEMA_COUNT}}

Total number of Schemata: {{SCHEMA_COUNT}}

7. 7. 1. 3. 4. The Indexes Tab

Tab

Total number of Schemata: {{SCHEMA_COUNT}}

Gambar 7. 10. Tab Indeks

Pilih indeks dengan mengklik kanan. Melakukan hal ini akan menampilkan informasi tentang indeks di bagian Kolom Indeks

To add an index, click the last row in the index list. Masukkan nama untuk indeks dan pilih jenis indeks dari kotak daftar drop-down. Pilih kolom atau beberapa kolom yang ingin Anda indeks dengan mencentang nama kolom di daftar Kolom Indeks. Anda dapat menghapus kolom dari indeks dengan menghapus tanda centang dari kolom yang sesuai

Anda juga dapat menentukan urutan indeks dengan memilih

Total number of Schemata: {{SCHEMA_COUNT}}

Total number of Schemata: {{SCHEMA_COUNT}}

Total number of Schemata: {{SCHEMA_COUNT}}

Total number of Schemata: {{SCHEMA_COUNT}}

7. 7. 1. 3. 5. Tab Kunci Asing

The

Total number of Schemata: {{SCHEMA_COUNT}}

Total number of Schemata: {{SCHEMA_COUNT}}

Untuk menambahkan kunci asing, klik baris terakhir dalam daftar

Total number of Schemata: {{SCHEMA_COUNT}}

Under Foreign Key Options choose an action for the update and delete events

Pilihannya adalah

• MEMBATASI

• RIAM

• SET NULL

• TIDAK ADA TINDAKAN

To modify any of the properties of a foreign key, simply select it and make the desired changes

7. 7. 1. 3. 6. The Triggers Tab

The

Total number of Schemata: {{SCHEMA_COUNT}}

7. 7. 1. 3. 7. Tab Partisi

If you wish to enable partitioning for your table check the Enable Partitioning check box. Doing this enables the partitioning options

Kotak drop-down Partition By menampilkan jenis partisi yang dapat Anda buat. Ini adalah

• Total number of Schemata: {{SCHEMA_COUNT}}

  _51

• Total number of Schemata: {{SCHEMA_COUNT}}

  _52

• Total number of Schemata: {{SCHEMA_COUNT}}

  _53

• Total number of Schemata: {{SCHEMA_COUNT}}

  54

• Total number of Schemata: {{SCHEMA_COUNT}}

  _55

• Total number of Schemata: {{SCHEMA_COUNT}}

  56

Gunakan kotak teks Parameter untuk menentukan parameter yang akan diberikan ke fungsi partisi, misalnya nilai kolom bilangan bulat

Choose the number of partitions from the Partition Count drop down list box. Jika Anda ingin mengonfigurasi partisi secara manual, centang kotak centang Manual. Melakukan hal ini memungkinkan masuknya nilai ke dalam tabel konfigurasi partisi. Entri dalam tabel ini adalah

• Total number of Schemata: {{SCHEMA_COUNT}}

  57

• Total number of Schemata: {{SCHEMA_COUNT}}

  _58

• Total number of Schemata: {{SCHEMA_COUNT}}

  59

• Total number of Schemata: {{SCHEMA_COUNT}}

  _60

• Total number of Schemata: {{SCHEMA_COUNT}}

  _61

• Total number of Schemata: {{SCHEMA_COUNT}}

  62

• Total number of Schemata: {{SCHEMA_COUNT}}

  63

Subpartisi juga tersedia. For more information about partitioning see Partitioning

7. 7. 1. 3. 8. Tab Opsi

The Options tab enables you to set several types of options. Ini dikelompokkan ke dalam bingkai berikut

• General Options

• Opsi Baris

• Opsi Penyimpanan

• Merge Table options

Each of these is discussed in more detail in the following sections

General Options

In the General Options frame, choose a pack keys option. Pilihannya adalah

Total number of Schemata: {{SCHEMA_COUNT}}

Total number of Schemata: {{SCHEMA_COUNT}}

Total number of Schemata: {{SCHEMA_COUNT}}

Total number of Schemata: {{SCHEMA_COUNT}}

Opsi Baris

To set the row format, choose the desired row format from the drop-down list. Lihat

Total number of Schemata: {{SCHEMA_COUNT}}

Pilihan ini adalah

• Bawaan

• Dynamic

• Fixed

• Compressed

• Redundant

• Kompak

Saat Anda mengharapkan tabel menjadi sangat besar, gunakan rata-rata. Baris, Min. Baris, dan Maks. Opsi baris untuk mengaktifkan server MySQL untuk mengakomodasi data Anda dengan lebih baik. Lihat

Total number of Schemata: {{SCHEMA_COUNT}}

Opsi Penyimpanan

Bagian

Total number of Schemata: {{SCHEMA_COUNT}}

Menggabungkan Opsi Tabel

Bagian Opsi ________0______71 digunakan untuk mengonfigurasi tabel MERGE di MyISAM. To create a MERGE table, select MERGE as your storage engine and then specify the tables you wish to MERGE in the Union Tables dialog

You can also specify the action the server should take when users attempt to perform INSERT statements on the merge table. Lihat Mesin Penyimpanan

Total number of Schemata: {{SCHEMA_COUNT}}

Total number of Schemata: {{SCHEMA_COUNT}}

7. 7. 1. 3. 9. The Inserts Tab

Gunakan tab

Total number of Schemata: {{SCHEMA_COUNT}}

To edit a record simply click the field you wish to change and enter the new data. Mengklik kanan baris menampilkan menu dengan item berikut

• Set Field(s) to NULL

• Hapus Baris

• Copy Row Content. Menyalin baris ke clipboard. String disalin dikutip, dan NULL dipertahankan

• Salin Konten Baris (tanpa tanda kutip). Copies the row to the clipboard. String tidak dikutip dan NULL disalin sebagai spasi

• Salin Konten Bidang. Menyalin nilai bidang yang dipilih ke papan klip. Strings are quoted

• Salin Konten Bidang (tanpa tanda kutip). Menyalin nilai bidang yang dipilih ke papan klip. String tidak dikutip

Note that the insert editor features a toolbar. Ini memiliki fungsi yang sama seperti yang dijelaskan dalam dan. Anda juga dapat mengarahkan kursor ke toolbar untuk menampilkan tooltips

Catatan apa pun yang Anda tambahkan akan dimasukkan saat Anda meneruskan merekayasa database (jika Anda memilih opsi

Total number of Schemata: {{SCHEMA_COUNT}}

Note when entering string values that there is slightly different behavior between the 5. 0, 5. 1 dan 5. 2 versi Meja Kerja MySQL

Untuk 5. 0 dan 5. 1 jika string dimasukkan tanpa tanda kutip di depan dan di belakang, Editor Sisipan menambahkan kutipan dan menghapus karakter yang memerlukannya. However, if quoted text is entered, the Inserts Editor carries out no further checks since it assumes a correctly escaped and quoted sequence has been entered

5. 2 menampilkan Editor Sisipan baru. Dalam hal ini pengguna memasukkan string tanpa mengutip atau keluar dan Editor Sisipan menangani semua mengutip dan keluar sesuai kebutuhan

Dimungkinkan untuk memasukkan fungsi, atau ekspresi lain, ke dalam bidang. Jika demikian, awalan

Total number of Schemata: {{SCHEMA_COUNT}}

Total number of Schemata: {{SCHEMA_COUNT}}

Total number of Schemata: {{SCHEMA_COUNT}}

Total number of Schemata: {{SCHEMA_COUNT}}

7. 7. 1. 3. 10. The Privileges Tab

Use the

Schema: Airlines
Schema: Airports

When this tab is first opened, all the roles that have been created are displayed in the list box on the right. Pindahkan peran yang ingin Anda kaitkan dengan tabel ini ke kotak daftar Peran di sebelah kiri. Do this by selecting a role and then clicking the < button. Gunakan tombol Shift untuk memilih beberapa peran yang bersebelahan dan tombol Ctrl untuk memilih peran yang tidak bersebelahan

To assign privileges to a role, click the role in the Roles list box. Melakukan ini akan menampilkan semua hak istimewa yang tersedia di kotak daftar Hak Istimewa yang Ditetapkan. Keistimewaan yang ditampilkan adalah

• Total number of Schemata: {{SCHEMA_COUNT}}

  _81

• Total number of Schemata: {{SCHEMA_COUNT}}

  _82

• Total number of Schemata: {{SCHEMA_COUNT}}

  _83

• Total number of Schemata: {{SCHEMA_COUNT}}

  _84

• Total number of Schemata: {{SCHEMA_COUNT}}

  _85

•     Report
      ------
      {{#COLUMNS}}
      Column Name: {{COLUMN_NAME}}
      {{/COLUMNS}}
    

  _9

• Total number of Schemata: {{SCHEMA_COUNT}}

  _87

• Total number of Schemata: {{SCHEMA_COUNT}}

  _88

• Total number of Schemata: {{SCHEMA_COUNT}}

  _89

•     Report
      ------
      {{#COLUMNS}}
      Column Name: {{COLUMN_NAME}}
      {{/COLUMNS}}
    

  _1

• Total number of Schemata: {{SCHEMA_COUNT}}

  _91

• Total number of Schemata: {{SCHEMA_COUNT}}

  _92

Anda dapat memilih untuk menetapkan semua hak istimewa kepada pengguna tertentu atau hak istimewa lainnya seperti yang tercantum sebelumnya. Hak istimewa yang tidak relevan dengan tabel tertentu, misalnya hak istimewa

Total number of Schemata: {{SCHEMA_COUNT}}

Jika peran telah diberi hak istimewa pada tabel tertentu, hak istimewa tersebut akan ditampilkan sebagai sudah dicentang di kotak daftar Hak Istimewa yang Ditetapkan

7. 7. 2. Creating Foreign Key Relationships

Kendala kunci asing hanya didukung untuk mesin penyimpanan ________0______94. For other storage engines the foreign key syntax is correctly parsed but not implemented. For more information see Foreign Keys

Menggunakan MySQL Workbench Anda dapat menambahkan kunci asing dari dalam editor tabel atau dengan menggunakan alat hubungan pada bilah alat vertikal Diagram EER. This section deals with adding a foreign key using the foreign key tools. To add a foreign key using the table editor see

Menggunakan alat grafis untuk menambahkan kunci asing paling efektif saat Anda membuat tabel dari bawah ke atas. Jika Anda telah mengimpor database menggunakan skrip SQL dan tidak perlu menambahkan bidang ke tabel Anda, Anda mungkin merasa lebih efektif untuk menentukan kunci asing menggunakan editor tabel

7. 7. 2. 1. Adding Foreign Key Relationships Using an EER Diagram

Ada enam alat kunci asing pada bilah alat vertikal di sisi kiri Diagram EER. These tools are

• Alat

  Total number of Schemata: {{SCHEMA_COUNT}}

  _95

• Alat

  Total number of Schemata: {{SCHEMA_COUNT}}

  _96

• Alat

  Total number of Schemata: {{SCHEMA_COUNT}}

  _97

• Alat

  Total number of Schemata: {{SCHEMA_COUNT}}

  _98

• Alat

  Total number of Schemata: {{SCHEMA_COUNT}}

  _99

• Alat

  Total number of Schemata: 2

  _00

Hubungan pengidentifikasi adalah hubungan di mana tabel anak tidak dapat diidentifikasi secara unik tanpa induknya. Biasanya ini terjadi ketika tabel perantara dibuat untuk menyelesaikan hubungan banyak ke banyak. Dalam kasus seperti itu, kunci utama biasanya merupakan kunci komposit yang dibuat dari kunci utama dari dua tabel asli. Hubungan yang mengidentifikasi ditunjukkan dengan garis tegas antara tabel dan hubungan yang tidak mengidentifikasi ditunjukkan dengan garis putus-putus

Buat atau seret dan lepas tabel yang ingin Anda sambungkan. Pastikan ada kunci utama dalam tabel yang akan berada di sisi "satu" hubungan. Klik alat yang sesuai untuk jenis hubungan yang ingin Anda buat. Jika Anda membuat hubungan satu-ke-banyak, pertama-tama klik tabel yang berada di sisi “banyak” dari hubungan tersebut, kemudian pada tabel yang berisi kunci yang direferensikan

Melakukan hal ini akan membuat bidang dalam tabel di banyak sisi hubungan. Nama default bidang ini adalah

Total number of Schemata: 2

Saat alat banyak-ke-banyak aktif, mengklik dua kali tabel akan membuat tabel asosiatif dengan hubungan banyak-ke-banyak. Agar alat ini berfungsi, harus ada kunci utama yang ditentukan di tabel awal

To edit the properties of a foreign key, double-click anywhere on the connection line that joins the two tables. Melakukan hal ini akan membuka editor hubungan

Mousing over a relationship connector highlights the connector and the related keys as shown in the following figure

Gambar 7. 11. Penghubung Relasi

Tabel

Total number of Schemata: 2

Total number of Schemata: 2

Total number of Schemata: 2

Total number of Schemata: 2

Total number of Schemata: 2

If the placement of a connection's caption is not suitable, you can change its position by dragging it to a different location. Jika Anda telah menetapkan teks tambahan, posisinya juga dapat diubah. (For more information about secondary captions see . Where the notation style allows,

Total number of Schemata: 2

The relationship notation style in is the default, crow's foot. If you are using a commercial version of MySQL Workbench you can change this. Untuk informasi lebih lanjut, lihat

You can select multiple connections by holding down the Ctrl key as you click a connection. This can be useful for highlighting specific relationships on an EER diagram

7. 7. 2. 2. Editor Relasi

Mengklik dua kali hubungan pada kanvas diagram EER akan membuka editor hubungan. Ini memiliki dua tab. Hubungan, dan Kunci Asing

Tab Hubungan

You can also add a secondary caption to a relationship and also a comment

Frame Visibility Setting digunakan untuk menentukan bagaimana relasi ditampilkan pada kanvas EER Diagram.

    Report
    ------

    {{! Main dictionary active}}
    {{#SCHEMATA}}  {{! SCHEMATA dictionary active}}
    {{#TABLES}}  {{! TABLES dictionary active}}
    {{#COLUMNS_LISTING}} {{! COLUMNS_LISTING dictionary active}}
    {{#COLUMNS}}  {{! COLUMNS dictionary active}}
    Column Name: {{COLUMN_NAME}} {{! COLUMN_NAME variable is looked-up, and found, in COLUMNS data dictionary}}
    {{/COLUMNS}}
    {{/COLUMNS_LISTING}}
    {{/TABLES}}
    {{/SCHEMATA}}

  

Gambar 7. 12. Konektor Terpisah

Konektor garis putus-putus digunakan untuk menunjukkan hubungan yang tidak dapat diidentifikasi. Gaya garis pemisah dapat digunakan dengan hubungan yang mengidentifikasi atau hubungan yang tidak mengidentifikasi. Ini hanya digunakan untuk tujuan tampilan dan tidak menunjukkan apa pun tentang sifat suatu hubungan

Tab Kunci Asing

The Foreign Key tab contains several frames. Referencing Table, Cardinality and Referenced Table

Kotak centang Wajib digunakan untuk memilih apakah tabel referensi dan tabel referensi wajib. Nilai default untuk kedua batasan ini adalah

    Report
    ------

    {{#SCHEMATA}}
    {{#TABLES}}
    {{#COLUMNS_LISTING}}
    {{#COLUMNS}}
    Schema Name: {{SCHEMA_NAME}} Column Name: {{COLUMN_NAME}}
    {{/COLUMNS}}
    {{/COLUMNS_LISTING}}
    {{/TABLES}}
    {{/SCHEMATA}}

  

Dalam bingkai Cardinality ada satu set tombol radio yang memungkinkan Anda memilih apakah hubungan itu satu-ke-satu atau satu-ke-banyak. Ada juga kotak centang yang memungkinkan Anda untuk menentukan apakah hubungan tersebut merupakan hubungan yang mengidentifikasi

7. 7. 2. 3. The Properties of a Connection

To select a connection, right-click it. Ketika koneksi dipilih, itu disorot dan propertinya ditampilkan di palet properti. The properties of a connection are quite different from the properties of other objects. Properti ini dijelaskan dalam daftar berikut

• Total number of Schemata: 2

  _10. Nama objek. Secara default, properti ini dipusatkan di atas jalur koneksi. Nilai standarnya adalah nama kunci asing

• Total number of Schemata: 2

  _11. Offset "x" pada teks

• Total number of Schemata: 2

  _12. The “y” offset of the caption

• Total number of Schemata: 2

  _13. Komentar yang terkait dengan hubungan

• Total number of Schemata: 2

  _14. Whether or not to show the relationship as a continuous line

• Total number of Schemata: 2

  _15. The “x” termination point of the caption offset

• Total number of Schemata: 2

  16. The “y” termination point of the caption offset

• Total number of Schemata: 2

  17. Keterangan sekunder. Lokasi default untuk keterangan tambahan ini dipusatkan di bawah garis koneksi

• Total number of Schemata: 2

  18. Offset "x" dari keterangan sekunder

• Total number of Schemata: 2

  _19. Offset "y" dari keterangan sekunder

• Total number of Schemata: 2

  _20. Apakah entitas itu wajib atau tidak. Untuk informasi lebih lanjut, lihat

• Total number of Schemata: 2

  _21. Salah jika hubungan adalah hubungan satu-ke-satu

• Total number of Schemata: 2

  22. Offset bagian tengah konektor

• Total number of Schemata: 2

  _23. ketika ini disetel, koneksi tidak akan disebarkan ke DDL. Itu hanyalah koneksi logis yang digambar pada diagram. Ini digunakan, misalnya, saat menggambar tabel MyISAM dengan hubungan visual, tetapi tanpa kunci asing

•     Report
      ------
  
      {{#SCHEMATA}}
      {{#TABLES}}
      {{#COLUMNS_LISTING}}
      {{#COLUMNS}}
      Schema Name: {{SCHEMA_NAME}} Column Name: {{COLUMN_NAME}}
      {{/COLUMNS}}
      {{/COLUMNS_LISTING}}
      {{/TABLES}}
      {{/SCHEMATA}}
  
    

  7. The name used to identify the connection on the EER Diagram canvas. Perhatikan bahwa ini bukan nama kunci asing

• Total number of Schemata: 2

  _25. Whether or not the referred entity is mandatory

• Total number of Schemata: 2

  26. Awal offset "x" dari teks

• Total number of Schemata: 2

  _27. The start of the “y” offset of the caption

Dalam kebanyakan kasus, Anda dapat mengubah properti hubungan menggunakan editor hubungan daripada palet

Total number of Schemata: 2

You can add views to a database either from the

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Total number of Schemata: {{SCHEMA_COUNT}}

7. 7. 3. 1. Menambahkan Tampilan ke Skema Fisik

Mengklik dua kali ikon

Total number of Schemata: 2

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Total number of Schemata: {{SCHEMA_COUNT}}

Total number of Schemata: 2

Total number of Schemata: 2

Menambahkan tampilan baru secara otomatis membuka editor tampilan yang terpasang di bagian bawah aplikasi. Menggunakan editor tampilan dijelaskan di

Right-clicking a table opens a pop-up menu with the following options

Tampilan apa pun yang ditambahkan ke

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Total number of Schemata: {{SCHEMA_COUNT}}

7. 7. 3. 2. Menambahkan Tampilan ke Diagram EER

Tampilan juga dapat ditambahkan ke Diagram EER menggunakan alat

Total number of Schemata: 2

Total number of Schemata: {{SCHEMA_COUNT}}

Mengklik ikon ini akan mengubah penunjuk tetikus menjadi penunjuk tampilan. Anda juga dapat mengubah penunjuk tetikus menjadi penunjuk tampilan dengan menekan tombol V

Memilih alat

Total number of Schemata: 2

Total number of Schemata: 2

Total number of Schemata: 2

Create a view by clicking anywhere on the EER Diagram canvas. Ini membuat tampilan baru dengan nama default

Total number of Schemata: 2

Right-clicking a view opens a pop-up menu. Dengan pengecualian opsi hapus, opsi menu ini berfungsi seperti yang dijelaskan di. Perilaku opsi hapus ditentukan oleh pengaturan opsi MySQL Workbench Anda. For more information, see

Anda dapat memanggil editor tampilan dengan mengklik dua kali objek tampilan di kanvas EER Diagram atau dengan mengklik dua kali tampilan di bagian

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Total number of Schemata: {{SCHEMA_COUNT}}

Ada tiga tab di bagian bawah view editor, tab View, Comments, dan Privileges. Menavigasi di antara tab yang berbeda menggunakan mouse atau dari keyboard dengan menekan Ctrl + Alt + Tab

Total number of Schemata: 2

Dari tab

Total number of Schemata: 2

• Ganti nama tampilan menggunakan kotak teks Nama

• Masukkan SQL untuk membuat tampilan menggunakan area teks SQL

• Comment a view using the Comments text area

The

Total number of Schemata: 2

Tab ini memungkinkan Anda memasukkan komentar untuk tampilan tertentu

The

Schema: Airlines
Schema: Airports

Tab

Schema: Airlines
Schema: Airports

Schema: Airlines
Schema: Airports

7. 7. 3. 4. Memodifikasi View menggunakan Properties Palette

Saat Anda memilih tampilan di kanvas EER Diagram, propertinya ditampilkan di palet

Total number of Schemata: 2

Total number of Schemata: 2

Untuk daftar properti yang dapat diakses melalui palet

Total number of Schemata: 2

7. 7. 4. Creating Routines and Routine Groups

Anda dapat menambahkan Grup Rutin ke database baik dari bagian Skema Fisik halaman Model MySQL atau dari Diagram EER. Rutinitas hanya dapat ditambahkan dari bagian Skema Fisik di halaman Model MySQL

MySQL Workbench menyatukan prosedur tersimpan dan fungsi tersimpan menjadi satu objek logis yang disebut Rutin. Grup Rutin digunakan untuk mengelompokkan rutinitas yang terkait. Anda dapat memutuskan berapa banyak Grup Rutin yang ingin Anda buat dan Anda dapat menggunakan Editor Grup Rutin untuk menetapkan rutinitas tertentu ke grup, menggunakan antarmuka seret dan lepas

Saat mendesain Diagram EER, Anda dapat menempatkan Grup Rutin di kanvas dengan menyeretnya dari Palet Katalog. Menempatkan rutinitas individu pada diagram tidak diperbolehkan, karena akan mengacaukan kanvas

7. 7. 4. 1. 1. Menambahkan Rutin ke Skema Fisik

Double-clicking the

Total number of Schemata: 2

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Total number of Schemata: {{SCHEMA_COUNT}}

Total number of Schemata: 2

Total number of Schemata: 2

Menambahkan rutinitas baru secara otomatis membuka editor rutin yang terpasang di bagian bawah aplikasi. Menggunakan editor rutin dijelaskan di

Mengklik kanan rutinitas membuka menu pop-up dengan opsi berikut

The cut and paste options are useful for copying routines between different schemata

Menghapus kode rutin dari tab Rutinitas Editor Grup Rutin akan menghapus objek rutin dari model

Untuk menghapus rutinitas dari grup rutin, gunakan kontrol pada tab Grup Rutin di Editor Grup Rutin

Tindakan opsi hapus bervariasi tergantung pada cara Anda mengonfigurasi MySQL Workbench. For more information, see

7. 7. 4. 1. 2. Editor Rutin

Anda dapat memanggil editor rutin dengan mengklik dua kali rutin di bagian

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Total number of Schemata: {{SCHEMA_COUNT}}

There are two tabs at the bottom of the routine editor, the Routine and the Privileges tabs. Navigate between different tabs using the mouse or from the keyboard by pressing Ctrl + Alt + Tab

7. 7. 4. 1. 2. 1.

Total number of Schemata: 2

From the

Total number of Schemata: 2

• Rename the routine using the Name text box

• Enter the SQL to create a routine using the SQL text area

7. 7. 4. 1. 2. 2. Tab

Schema: Airlines
Schema: Airports

Tab

Schema: Airlines
Schema: Airports

Schema: Airlines
Schema: Airports

Privileges are only available in the Standard Edition of MySQL Workbench

7. 7. 4. 2. 1. Adding Routine Groups to the Physical Schemata

Mengklik dua kali ikon

Total number of Schemata: 2

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Total number of Schemata: {{SCHEMA_COUNT}}

Total number of Schemata: 2

Total number of Schemata: 2

Menambahkan grup rutin baru secara otomatis membuka editor grup rutin yang terpasang di bagian bawah aplikasi. Menggunakan editor grup rutin dijelaskan di

Mengklik kanan grup rutin membuka menu pop-up dengan opsi berikut

Opsi potong dan tempel berguna untuk menyalin grup rutin di antara skema yang berbeda

Menghapus grup rutin dari halaman

Total number of Schemata: {{SCHEMA_COUNT}}

Grup rutin apa pun yang ditambahkan ke

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Total number of Schemata: {{SCHEMA_COUNT}}

7. 7. 4. 2. 2. Menambahkan Grup Rutin ke Diagram EER

Grup rutin juga dapat ditambahkan ke Diagram EER menggunakan alat

Total number of Schemata: 2

Total number of Schemata: {{SCHEMA_COUNT}}

Mengklik mouse pada ikon ini akan mengubah penunjuk mouse menjadi penunjuk grup rutin. Anda juga dapat mengubah penunjuk tetikus menjadi penunjuk rutin dengan menekan tombol G

Memilih alat

Total number of Schemata: 2

Total number of Schemata: 2

Total number of Schemata: 2

Create a routine group by clicking anywhere on the EER Diagram canvas. This creates a new routine group with the default name

Total number of Schemata: 2

Right-clicking a routine group opens a pop-up menu. With the exception of the delete option and rename options these menu options function as described in . There is no rename option and the behavior of the delete option is determined by your MySQL Workbench options settings. For more information, see

7. 7. 4. 2. 3. The Routine Group Editor

You can invoke the routine group editor by double-clicking a routine group object on the EER Diagram canvas or by double clicking a routine group in the

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Total number of Schemata: {{SCHEMA_COUNT}}

There are two tabs at the bottom of the routine editor, the Routine group and the Privileges tabs. Navigate between different tabs using the mouse or from the keyboard by pressing Ctrl + Alt + Tab

7. 7. 4. 2. 3. 1. The

Total number of Schemata: 2

From the

Total number of Schemata: 2

• Rename the routine group using the Name text box

• Add routines to the group by dragging and dropping them

• Add comments to the routine group

7. 7. 4. 2. 3. 2. The

Schema: Airlines
Schema: Airports

The

Schema: Airlines
Schema: Airports

Schema: Airlines
Schema: Airports

Privileges are only available in the Standard Edition of MySQL Workbench

7. 7. 4. 2. 3. 3. Modifying a Routine Group Using the Properties Palette

When you select a routine group on the EER Diagram canvas, its properties are displayed in the

Total number of Schemata: 2

Total number of Schemata: 2

Untuk daftar properti yang dapat diakses melalui palet

Total number of Schemata: 2

You can add layers to a database only from an EER Diagram. Layers are used to help organize objects on the canvas. Typically, related objects are added to the same layer; for example, you may choose to add all your views to one layer

7. 7. 5. 1. Adding Layers to an EER Diagram

Layers are added to an EER Diagram using the

    Report
    ------

    {{! Main dictionary active}}
    {{#SCHEMATA}}  {{! SCHEMATA dictionary active}}
    {{#TABLES}}  {{! TABLES dictionary active}}
    {{#COLUMNS_LISTING}} {{! COLUMNS_LISTING dictionary active}}
    {{#COLUMNS}}  {{! COLUMNS dictionary active}}
    Column Name: {{COLUMN_NAME}} {{! COLUMN_NAME variable is looked-up, and found, in COLUMNS data dictionary}}
    {{/COLUMNS}}
    {{/COLUMNS_LISTING}}
    {{/TABLES}}
    {{/SCHEMATA}}

  

Total number of Schemata: {{SCHEMA_COUNT}}

Total number of Schemata: 2

Clicking the mouse on this icon changes the mouse pointer to a layer pointer. You can also change the mouse pointer to a layer pointer by pressing the L key

Choosing the

    Report
    ------

    {{! Main dictionary active}}
    {{#SCHEMATA}}  {{! SCHEMATA dictionary active}}
    {{#TABLES}}  {{! TABLES dictionary active}}
    {{#COLUMNS_LISTING}} {{! COLUMNS_LISTING dictionary active}}
    {{#COLUMNS}}  {{! COLUMNS dictionary active}}
    Column Name: {{COLUMN_NAME}} {{! COLUMN_NAME variable is looked-up, and found, in COLUMNS data dictionary}}
    {{/COLUMNS}}
    {{/COLUMNS_LISTING}}
    {{/TABLES}}
    {{/SCHEMATA}}

  

    Report
    ------

    {{#SCHEMATA}}
    {{#TABLES}}
    {{#COLUMNS_LISTING}}
    {{#COLUMNS}}
    Column Name: {{COLUMN_NAME}}
    {{/COLUMNS}}
    {{/COLUMNS_LISTING}}
    {{/TABLES}}
    {{/SCHEMATA}}

  

Total number of Schemata: 2

Create a layer by clicking anywhere on the EER Diagram canvas and, holding the left mouse button down, draw a rectangle of a suitable size. This creates a new layer with the default name

Total number of Schemata: 2

Find below an image of a layer containing a number of views

Figure 7. 13. The Layer Object

Use the

    Report
    ------

    {{#SCHEMATA}}
    {{#TABLES}}
    {{#COLUMNS_LISTING}}
    {{#COLUMNS}}
    Schema Name: {{SCHEMA_NAME}} Column Name: {{COLUMN_NAME}}
    {{/COLUMNS}}
    {{/COLUMNS_LISTING}}
    {{/TABLES}}
    {{/SCHEMATA}}

  

Total number of Schemata: 2

Right-clicking a layer opens a pop-up menu with the following options

The cut and copy options are useful for copying layers between different schemata

Since layers are not schema objects, no confirmation dialog box opens when you delete a layer regardless of how you have configured MySQL Workbench. Deleting a layer does not delete schema objects from the catalog

7. 7. 5. 1. 1. Adding Objects to a Layer

Add an object to a layer by dragging and dropping it directly from the

Total number of Schemata: {{SCHEMA_COUNT}}

Locking objects to a layer prevents their accidental removal. You cannot remove them simply by clicking and dragging; in order to remove an object, you also need to press the Ctrl key while dragging it

As a visual cue that the object is being "locked", the outline of the layer is highlighted as the object is dragged over it

If you drag a layer over a table object, the table object will automatically be added to the layer. This also works for multiple table objects

Note that layers cannot be nested, that is, a layer cannot contain another layer object

7. 7. 5. 2. Modifying a Layer using the Properties Palette

When you select a layer on the EER Diagram canvas, its properties are displayed in the

Total number of Schemata: 2

Total number of Schemata: 2

In some circumstances you may want to make a layer invisible. To do this, select the layer and, in the

Total number of Schemata: 2

    Report
    ------

    {{#SCHEMATA}}
    {{#TABLES}}
    {{#COLUMNS_LISTING}}
    {{#COLUMNS}}
    Column Name: {{COLUMN_NAME}}
    {{/COLUMNS}}
    {{/COLUMNS_LISTING}}
    {{/TABLES}}
    {{/SCHEMATA}}

  

    Report
    ------

    {{! Main dictionary active}}
    {{#SCHEMATA}}  {{! SCHEMATA dictionary active}}
    {{#TABLES}}  {{! TABLES dictionary active}}
    {{#COLUMNS_LISTING}} {{! COLUMNS_LISTING dictionary active}}
    {{#COLUMNS}}  {{! COLUMNS dictionary active}}
    Column Name: {{COLUMN_NAME}} {{! COLUMN_NAME variable is looked-up, and found, in COLUMNS data dictionary}}
    {{/COLUMNS}}
    {{/COLUMNS_LISTING}}
    {{/TABLES}}
    {{/SCHEMATA}}

  

    Report
    ------

    {{#SCHEMATA}}
    {{#TABLES}}
    {{#COLUMNS_LISTING}}
    {{#COLUMNS}}
    Column Name: {{COLUMN_NAME}}
    {{/COLUMNS}}
    {{/COLUMNS_LISTING}}
    {{/TABLES}}
    {{/SCHEMATA}}

  

    Report
    ------

    {{#SCHEMATA}}
    {{#TABLES}}
    {{#COLUMNS_LISTING}}
    {{#COLUMNS}}
    Column Name: {{COLUMN_NAME}}
    {{/COLUMNS}}
    {{/COLUMNS_LISTING}}
    {{/TABLES}}
    {{/SCHEMATA}}

  

Total number of Schemata: 2

For a list of the properties accessible through the

Total number of Schemata: 2

    Report
    ------

    {{! Main dictionary active}}
    {{#SCHEMATA}}  {{! SCHEMATA dictionary active}}
    {{#TABLES}}  {{! TABLES dictionary active}}
    {{#COLUMNS_LISTING}} {{! COLUMNS_LISTING dictionary active}}
    {{#COLUMNS}}  {{! COLUMNS dictionary active}}
    Column Name: {{COLUMN_NAME}} {{! COLUMN_NAME variable is looked-up, and found, in COLUMNS data dictionary}}
    {{/COLUMNS}}
    {{/COLUMNS_LISTING}}
    {{/TABLES}}
    {{/SCHEMATA}}

  

You can add notes to a database only from the

    Report
    ------
    {{#COLUMNS}}
    Column Name: {{COLUMN_NAME}}
    {{/COLUMNS}}
  

Total number of Schemata: {{SCHEMA_COUNT}}

Double-clicking the

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

    Report
    ------
    {{#COLUMNS}}
    Column Name: {{COLUMN_NAME}}
    {{/COLUMNS}}
  

Total number of Schemata: {{SCHEMA_COUNT}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Adding a new note automatically opens the note editor docked at the bottom of the application. Using the note editor is described in

Right-clicking a note opens a pop-up menu with the following options

The cut and copy options are useful for copying notes between different schemata

Notes can only be added on the

Total number of Schemata: {{SCHEMA_COUNT}}

You can invoke the note editor by double-clicking a note object in the

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Total number of Schemata: {{SCHEMA_COUNT}}

Menggunakan editor Anda dapat mengubah nama catatan atau isinya

7. 7. 7. Membuat Objek Teks

Objek teks hanya berlaku untuk diagram EER. Mereka dapat digunakan untuk tujuan dokumentasi, misalnya, untuk menjelaskan pengelompokan objek skema. Mereka juga berguna untuk membuat judul diagram EER jika Anda memutuskan untuk mengekspor diagram sebagai file PDF atau PNG

7. 7. 7. 1. Menambahkan Objek Teks ke Diagram EER

Objek teks dapat ditambahkan ke Diagram EER menggunakan alat

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Total number of Schemata: {{SCHEMA_COUNT}}

Mengklik mouse pada ikon ini akan mengubah pointer mouse menjadi pointer objek teks. Anda juga dapat mengubah penunjuk tetikus menjadi penunjuk objek teks dengan menekan tombol N

Memilih alat

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Total number of Schemata: 2

Create a text object by clicking anywhere on the EER Diagram canvas. This creates a new text object with the default name

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Right-clicking a text object opens a pop-up menu. These menu options are identical to the options for other objects. However, since a text object is not a database object, there is no confirmation dialog box when you delete a text object

7. 7. 7. 2. The Text Object Editor

You can invoke the text object editor by double-clicking a text object on the EER Diagram canvas. Doing this opens the editor docked at the bottom of the application. Double-clicking the text object table undocks the editor. Double-click the title bar to redock it. Any number of text objects may be open at the same time. Each additional text objects appears as a tab at the top of the text editor

Using the editor you can change the name of a text object or its contents

7. 7. 7. 2. 1. Modifying a Text Object Using the

Total number of Schemata: 2

8 Palette

When you select a text object on the EER Diagram canvas, its properties are displayed in the

Total number of Schemata: 2

Total number of Schemata: 2

Untuk daftar properti yang dapat diakses melalui palet

Total number of Schemata: 2

There is no property in the

Total number of Schemata: 2

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Images only exist on the EER Diagram canvas; you can only add them from the EER Diagram window

7. 7. 8. 1. Adding Images to an EER Diagram

Images can be added to an EER Diagram using the

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Total number of Schemata: {{SCHEMA_COUNT}}

Clicking the mouse on this icon changes the mouse pointer to an image pointer. You can also change the mouse pointer to an image pointer by pressing the I key

Create a image by clicking anywhere on the EER Diagram canvas. This opens a file open dialog box. Select the desired image, and close the dialog box to create an image on the canvas. Untuk kembali ke pointer mouse default, klik ikon panah di bagian atas toolbar vertikal

Right-clicking this object opens a pop-up menu with the following options

These menu options function in exactly the same way as they do for other objects on an EER diagram. However, images are not database objects so there is no confirmation dialog box when they are deleted

7. 7. 8. 2. The Image Editor

You can invoke the image editor by double-clicking a image object on an EER Diagram canvas. Doing this opens the image editor docked at the bottom of the application. Double-clicking the image editor tab undocks the editor. Double-click the title bar to redock it. Any number of images may be open at the same time. Each additional image appears as a tab at the top of the image editor,

From the

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

• Rename the image using the Name text box

• Browse for an image using the Browse button

7. 7. 9. Reverse Engineering

Using MySQL Workbench you can reverse engineer a database using a MySQL create script or you can connect to a live MySQL server and import a single database or a number of databases. Reverse engineering using a MySQL DDL script applies to all versions of MySQL Workbench; reverse engineering a database directly from a MySQL server applies to commercial versions of MySQL Workbench only

7. 7. 9. 1. Reverse Engineering Using a Create Script

You can create a data definition (DDL) script by executing the

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

If you plan to redesign a database within MySQL Workbench and then export the changes, be sure to retain a copy of the original DDL script. You will need the original script to create an

    Report
    ------
    {{#COLUMNS}}
    Column Name: {{COLUMN_NAME}}
    {{/COLUMNS}}
  

Use the

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

If your script creates a database, a new physical schemata tab is created on the

Total number of Schemata: {{SCHEMA_COUNT}}

Any database objects may be imported from a script file in this fashion; tables, views, routines, and routine groups. Any indexes, keys, and constraints are also imported. Objects imported using an SQL script can be manipulated within MySQL Workbench in the same way that any other objects can

See for a tutorial on reverse engineering the

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

7. 7. 9. 2. Reverse Engineering a Live Database

This section explains how to reverse engineer a live database using MySQL Workbench

Figure 7. 14. Reverse Engineer Database Wizard

The first page of the wizard enables you to set up a connection to the live database you wish to reverse engineer. This enables you to set up a new connection, or select a previously created connection. Typical information required for the connection includes hostname, username and password

Once this information has been entered, or you have selected a stored connection, click the Next button to proceed to the next page

Figure 7. 15. Connect to DBMS

Review the displayed information to make sure that the connection did not generate errors, then click Next

On the next page you can select the database schema you want to connect to among those available on the server. Cukup klik kotak centang atau kotak centang yang terkait dengan skema yang ingin Anda proses

Figure 7. 16. Select Schemata

Setelah Anda memilih skema yang diinginkan, klik tombol Berikutnya untuk melanjutkan

The wizard then displays the tasks it carried out and summarizes the results of the operation

Figure 7. 17. Fetch Object Info

Review the results before clicking Next to continue

The next page is the

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Gambar 7. 18. Pilih Objek

For the Import MySQL Table Objects section, if you click the Show Filter button the following page is displayed

Figure 7. 19. Show Filter

This enables you to select specific tables that you wish to import. Having selected the desired tables you can optionally hide the filter by clicking the Hide Filter button

The other sections, such as MySQL Routine Objects, have similar filters available

You can click Execute to continue to the next page

The wizard then displays the tasks that have been carried out and whether the operation was successful or not. If errors were generated then you can click the Show Logs button to see the nature of the errors

Figure 7. 20. Progress

Click Next to continue to the next page

The final screen of the wizard provides a summary of the reverse engineered objects

Figure 7. 21. Results

Click Finish to exit the wizard

7. 7. 9. 2. 1. Errors During Reverse Engineering

During reverse engineering the application checks for tables and views that duplicate existing names and disallows duplicate names if necessary. If you attempt to import an object that duplicates the name of an existing object you will be notified with an error message. To see any errors that have occurred during reverse engineering you can click the button Show Logs. This will create a panel containing a list of messages, including any error messages than may have been generated. Click the Hide Logs button to close the panel

Figure 7. 22. Message Log

If you wish to import an object with the same name as an existing object, rename the existing object before reverse engineering

If you import objects from more than one schema, there will be a tab in the

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Total number of Schemata: {{SCHEMA_COUNT}}

You cannot reverse engineer a live database that has the same name as an existing schema. If you wish to do this, first rename the existing schema

7. 7. 10. Forward Engineering

It is possible to forward engineer a database using an SQL script or by connecting to a live database

7. 7. 10. 1. Forward Engineering Using SQL Scripts

If you choose to create a database, there are a number of export options that you may choose from

7. 7. 10. 1. 1. Membuat Skema

Figure 7. 23. SQL Export Options

The SQL Export Options displays the following facilities

Output SQL Script File

You can enter the name of your output file by entering it into the Output SQL Script File text box, or by using the Browse button to select a file. If this text box is left blank you will be able to view the generated script, but it will not be saved to a file

Generate DROP Statements Before Each CREATE Statement

Omit Schema Qualifier in Object Names

Generate Separate CREATE INDEX Statements

Choosing this option creates separate statements for index creation instead of creating indexes as part of a

Total number of Schemata: {{SCHEMA_COUNT}}

Add SHOW WARNINGS after every DDL statement

Do Not Create Users. Only Export Privileges

To update the privileges of existing users as opposed to creating new users, select this check box. Exporting privileges for nonexistent users will result in errors when you execute the

Total number of Schemata: {{SCHEMA_COUNT}}

Generate INSERT Statements for Tables

If you have added any records to a table using the Insert tab of the MySQL Table Editor, choose this option. For more information about inserting records see

Clicking Next takes you to the SQL Object Export Filter page where you can select the objects you wish to export

Figure 7. 24. SQL Object Export Filter

Precise control over the objects to be exported can be fine tuned by clicking the Show Filter button. Once the objects to be exported have been selected it is possible to reduce the expanded panel by clicking the same button, now labelled Hide Filter

Having selected the objects you wish to export you can click the Next button to review the script that has been generated

Figure 7. 25. Review Generated Script

The Finish button saves the script file and exits. You may return to the previous screen using the Back button

You can then use the saved script to create a database

7. 7. 10. 1. 2. Altering a Schema

Figure 7. 26. Options

This first screen enables you to select a SQL script and compare it with the model currently in MySQL Workbench. The difference between the two models will be used to create an alter script that can be used to modify the target schema so that it matches the model held in MySQL Workbench. You can also simply view the script generated, rather than saving it to a file, by leaving the Output File text box empty

The script selected as the Input File must use full schema qualifiers, such as

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Pressing Next brings you to the Review SQL Script screen

Figure 7. 27. Naskah

Here you can review and change the alter script that will be generated. Make any changes you wish and, if you are happy with the changes, save the

    Report
    ------
    {{#COLUMNS}}
    Column Name: {{COLUMN_NAME}}
    {{/COLUMNS}}
  

The generated script can then be used to update the database

7. 7. 10. 2. Forward Engineering to a Live Server

Use forward engineering to export your schema design to a MySQL server

The first page to be displayed is Catalog Validation (validation is only available in the Standard Edition)

Figure 7. 28. Validasi Katalog

Klik Jalankan Validasi untuk memvalidasi katalog

Klik Berikutnya untuk melanjutkan

The next page enables you to set options for the database to be created. These options are as described in

Figure 7. 29. Options

Select the required options and then click Next

The next page enables you to select the objects to forward engineer

Figure 7. 30. Select Objects to Forward Engineer

To select a subset of objects to forward engineer use the Show Filter/Hide Filter button, and then select specific objects. Once you have selected your objects click Next to continue

On the

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Figure 7. 31. Review Script

Click Next to continue if you are satisfied with the generated script

The next step of the process is to connect to a MySQL server in order to create the new database schema. This page enables you to use a previously stored connection, or enter the connection parameters

Figure 7. 32. Set parameters for connecting to a DBMS

Once the connection parameters have been set click Execute. The next page of the wizard displays the results of the forward engineering process

Figure 7. 33. Set parameters for connecting to a DBMS

You can confirm the creation of the schema by connecting to the target MySQL server and issuing the

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

7. 7. 10. 3. Database Synchronization

It is possible to synchronize a model in MySQL Workbench with a live database. By default, the synchronization process will change the live database to be the same as the model, but this is configurable during the synchronization process

MySQL Workbench enables control over the direction of synchronization, and the objects synchronized, in a completely flexible way. You can choose to synchronize only certain tables, allow synchronization to the live database only, allow synchronization from the live database to the model only, or a combination of directions. In effect you have complete control as to whether the synchronization is unidirectional or bidirectional, and which objects exactly are subject to synchronization. This is all controlled in the Select Changes to Apply page of the synchronization wizard

Figure 7. 34. Model and Database Differences

In the above example the live database consists of

Total number of Schemata: {{SCHEMA_COUNT}}

Total number of Schemata: {{SCHEMA_COUNT}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

The next example shows how the direction of synchronization can be changed

Figure 7. 35. Controlling Synchronization Direction

In this case the synchronization direction has been changed so that rather than the default action of

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

For convenience the wizard provides three additional buttons to allows synchronization directions to be applied to a group of selected changes. The Update Model button causes the selected changes to only be applied to the model itself

Figure 7. 36. Update Model Button

In the above example

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

The Ignore button causes the selected changes to be ignored, no synchronization will take place for those changes

Figure 7. 37. Ignore Button

In the above example no changes would take place

The Update Source button causes the selected changes to only update the live database

Figure 7. 38. Update Source Button

In this example

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

It is also possible to control individual changes by clicking the arrows. Clicking an arrow causes it to change between the three available synchronization directions

Figure 7. 39. Click arrows to change direction of synchronization

In the above example

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

7. 7. 10. 4. Creating a Catalog Diff Report

Having started the wizard the first step is to specify the catalogs you wish to compare. For example, you may simply wish to compare your live database against your current MySQL Workbench model

Figure 7. 40. Catalog Sources

You then proceed through the wizard, providing connection information if accessing a live database. The wizard will then produce a catalog diff report showing the differences between the compared catalogs

Figure 7. 41. Catalog Diff Report

This chapter contains three short tutorials intended to familiarize you with the basics of MySQL Workbench. These tutorials show how MySQL Workbench can be used both to design and to document databases

Creating a database from scratch is the focus of and exploring the graphic design capabilities of MySQL Workbench is touched upon in . Both these tutorials show the database design capabilities of MySQL Workbench

Importing an SQL data definition script is probably the quickest way to familiarize yourself with MySQL Workbench—this tutorial makes use of the

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

7. 8. 1. Importing a Data Definition SQL Script

For this tutorial use the

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

If the file was successfully imported, the application's status bar reads,

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Yo may also wish to remove the default schema tab,

Schema: Airlines
Schema: Airports

To view all the objects in the

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Once you've expanded the window, all the objects in the

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

For a complete description of importing a MySQL create script see

7. 8. 1. 1. Adding an EER Diagram

Untuk membuat diagram EER untuk database

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Total number of Schemata: {{SCHEMA_COUNT}}

The

Total number of Schemata: {{SCHEMA_COUNT}}

Find the sakila schema and expand the view of its objects by clicking the + button to the left of the schema name. Expand the tables list in the same way

You can add tables to the EER canvas by picking them up from the Catalog panel and placing them on the canvas. Drop the

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Figure 7. 42. Adding Tables to the Canvas

MySQL Workbench automatically discovers that

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Choose the

Total number of Schemata: 2

Total number of Schemata: 2

Total number of Schemata: 2

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Changing the color of a table is a good way to identify a table quickly—something that becomes more important as the number of tables increases. Changing the color of a table is also an easy way to identify a table in the

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

7. 8. 2. Using the Default Schema

When you first open MySQL Workbench a default schema,

Schema: Airlines
Schema: Airports

Figure 7. 43. The Default Schema

To change the name of the default schema, double-click the schema tab. This opens a schema editor window docked at the bottom of the application. To undock or redock this window, simply double-click anywhere in the editor title bar

To rename the schema, use the text box labeled Name. Setelah Anda mengganti nama skema, ikon petir muncul rata kanan di kotak teks Nama, menunjukkan bahwa perubahan lain sedang menunggu. Click the Comments text area and a dialog box opens asking if you wish to rename all schema occurrences. Clicking Yes ensures that your changes are propagated throughout the application. Add comments to the database and change the collation if you wish. Close the schema editor by clicking the x button

7. 8. 2. 1. Creating a New Table

Create a new table by double-clicking the Add Table icon in the

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Use the first tab of the table editor to change the name, collation, and engine. You may also add a comment

Add columns to the new table by selecting the Columns tab. Use the default column name or enter a new name of your choosing. Use the Tab key to move to the next column and set the column's data type

Altering the table by adding indexes or other features is also easily done using the table editor

7. 8. 2. 2. Creating Other Schema Objects

Additional objects such as views or routines can be added in the same way as tables

Any objects you have created can be found in the Catalog palette on the right. To view these schema objects select the Catalog tab in the middle palette on the right. View all the objects by clicking the + button to the left of the schema name

On the

Total number of Schemata: {{SCHEMA_COUNT}}

Total number of Schemata: {{SCHEMA_COUNT}}

Figure 7. 44. Adding an EER Diagram

From an EER diagram page you can graphically design a database

The tools in the vertical toolbar on the left of the EER Diagram tab are used for designing an EER diagram. Start by creating a table using the table tool. The table tool is the rectangular grid in the middle of the vertical toolbar. Mousing over it shows the message,

Schema: Airlines
Schema: Airports

Clicking this tool changes the mouse pointer to a hand with a rectangular grid. Create a table on the canvas by clicking anywhere on the

Total number of Schemata: {{SCHEMA_COUNT}}

The table name defaults to

Total number of Schemata: {{SCHEMA_COUNT}}

Schema: Airlines
Schema: Airports

Pressing Tab or Enter while the cursor is in the table name text box, selects the Columns tab of the table editor and creates a default column named,

Schema: Airlines
Schema: Airports

Pressing Tab or Enter again sets the focus on the

Schema: Airlines
Schema: Airports

Schema: Airlines
Schema: Airports

Pressing Tab yet again and the focus shifts to adding a second column. Add a

Total number of Schemata: 2

Schema: Airlines
Schema: Airports

7. 8. 3. 2. Create a Foreign Key

Select the table tool again and place another table on the canvas. Name this table

Schema: Airlines
Schema: Airports

Schema: Airlines
Schema: Airports

First click the

Schema: Airlines
Schema: Airports

Schema: Airlines
Schema: Airports

Schema: Airlines
Schema: Airports

Revert to the default mouse pointer by clicking the arrow at the top of the vertical toolbar. Click on the

Schema: Airlines
Schema: Airports

Click the Foreign key Name text box. Tabel yang direferensikan harus ditampilkan di kolom Tabel yang Direferensikan dan kolom yang sesuai di kolom Kolom yang Direferensikan

To delete the relationship between two tables, click the line joining the tables and then press Ctrl Delete

Experiment with the other tools on the vertical toolbar. Hapus hubungan dengan memilih alat penghapus dan mengklik garis yang menghubungkan dua tabel. Create a view, add a text object, or add a layer

7. 8. 4. Documenting the {{#SCHEMATA}} Schema: {{SCHEMA_NAME}} {{/SCHEMATA}}44 Database

This chapter highlights the capabilities of MySQL Workbench as a documentation tool using the

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Anda juga dapat melihat bagaimana tabel terkait;

7. 8. 4. 1. File PNG dari

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

_44 Database

Figure 7. 45. The

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

The object notation style used in is

Schema: Airlines
Schema: Airports

As the connection lines show, each table is related to at least one other table in the database (with the exception of the

Schema: Airlines
Schema: Airports

Total number of Schemata: 2

Schema: Airlines
Schema: Airports

Schema: Airlines
Schema: Airports

Schema: Airlines
Schema: Airports

Identifying and nonidentifying relationships are indicated by solid and broken lines respectively. For example, the foreign key

Schema: Airlines
Schema: Airports

Schema: Airlines
Schema: Airports

Schema: Airlines
Schema: Airports

{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}

Schema: Airlines
Schema: Airports

The printing menu options are grayed if an EER Diagram is not active. The menu options are as follows

• Use this option to choose the paper size, orientation, and margins

• Use this option to send your EER Diagram directly to the printer. This option generates a preview before printing. From the preview you can adjust the scale of the view and also choose a multi-page view. Clicking the printer icon at the top left of this window, prints the currently selected EER Diagram. Close the print preview window if you need to adjust the placement of objects on the EER Diagram canvas

• Use this option to create a PDF file of your EER Diagram

• Use this option to create a PostScript file of your EER Diagram

7. 10. MySQL Workbench Schema Validation Plugins (Commercial Version)

MySQL Workbench provides validation modules so that you can test your models before implementing them

The tasks performed by the validation modules are outlined in what follows

7. 10. 1. General Validation

The types of validation and examples that violate validation are listed in what follows

• Empty Content validation

  • A table with no columns

  • A routine or view with no SQL code defined

  • A routine group containing no routines

  • A table, view, or routine not referenced by at least one role

  • Seorang pengguna tanpa hak istimewa

  • Objek seperti tabel yang tidak muncul pada setidaknya satu Diagram EER

• Table Efficiency Validation

  • A table with no primary key

  • A primary key that does not use an integer-based data type

  • A foreign key that refers to a column with a different data type

• Duplicated Identifiers Validation

  • Duplicate object names

  • Duplicate role or user names

  • Duplicate index or routine names

• Consistency Validation

  • Use of the same column with columns of differing data types

• Logic Validation

  • A foreign key that refers to a column other than the primary key in the source table

  • Any object that is object is either read- or write-only by role definition

  • Placeholder objects left over from reverse engineering

7. 10. 2. MySQL-Specific Validation

The types of MySQL-specific validation and examples that violate validation are listed in the following

• Integrity Violation

  • An object name longer than the maximum allowed

  • A foreign key defined for an engine type that doesn't support foreign keys (not yet implemented)

  • A view or routine that references a nonexistent table (not yet implemented)

  • A default value that does not match a column's data type

  • An invalid partitioning scheme

• Syntax Violation

  • A routine, trigger, or view with incorrect SQL syntax

  • A reserved keyword used as an identifier

  • Use of an invalid character

7. 11. Customizing DBDoc Model Reporting Templates

This document aims to provide an overview of creating and modifying DBDoc Model Reporting templates, as used by MySQL Workbench

The MySQL Workbench DBDoc Model Reporting system is based on the Google Template System. This document does not attempt to explain the Google Template System in detail. The Google document How To Use the Google Template System provides a useful overview of how the Google Template System works

The templates employed by the DBDoc Model Reporting system are text files that contain

Schema: Airlines
Schema: Airports

Markers can be of six types

1. Template Include

2. Comment

3. Set delimiter

4. Pragma

5. Variable

6. Section start and Section end

The last two are the most commonly used in MySQL Workbench templates and these important markers will be briefly described in the following sections

1. Variables

   The use of variables in the templates is straightforward. Any variables denoted by markers in the template file, will be replaced by their corresponding data, prior to the output file being generated. The mapping between variables and their corresponding data is stored by MySQL Workbench in what is known as a Data Dictionary. In the data dictionary the variable name is the key and the variable's corresponding data is the value. The data dicionaries are built by MySQL Workbench and filled with the data contained in the model being processed

   Sebagai contoh, cuplikan kode berikut menunjukkan bagian dari file template

   Total number of Schemata: {{SCHEMA_COUNT}}

   In the generated output file the variable {{SCHEMA_COUNT}} will be replaced by the number of schemata in the model

   Total number of Schemata: 2

   Variabel dapat muncul sebanyak yang diperlukan dalam file template

2. Sections

   Bagian digunakan untuk melakukan iterasi dalam template. When MySQL Workbench exchanges the variables in a section for data it will do so iteratively, using all data in the data dictionary in which the variable is defined. MySQL Workbench builds the data dictionaries according to the model currently being processed

   Again, this is best illustrated by example

   {{#SCHEMATA}}
   Schema: {{SCHEMA_NAME}}
   {{/SCHEMATA}}

   In the previous code snippet the section start is indicated by the

   Schema: Airlines
   Schema: Airports

   35 marker. Akhir bagian ditandai dengan penanda ________28______36. When the template is processed, MySQL Workbench will note the section and iterate the section until the variable data for

   Schema: Airlines
   Schema: Airports

   37 in the corresponding data dictionary is exhausted. For example, if the model being processed contains two schemata, the output for the section might resemble the following

   Schema: Airlines
   Schema: Airports

   That is, the model contains two schemata, Airlines and Airports

Data Dictionaries

It is important to understand the relationship between sections and data dictionaries in more detail. In a data dictionary the key for a variable is the variable name, a marker. The variable value is the variable's data. The entry for a section in a data dictionary is different. For a section entry in a data dictionary, the key is the section name, the marker. However, the value associated with the key is a list of data dictionaries. In MySQL Workbench each section is usually associated with a data dictionary. You can think of a section as activating its associated dictionary (or dictionaries)

When a template is processed, data dictionaries are loaded in a hierarchical pattern, forming a tree of data dictionaries. This is illustrated by the following table

Data DictionaryLoads Data DictionaryMAINSCHEMATASCHEMATATABLES, COLUMNS (Detailed is true), FOREIGN_KEYS (Detailed is true), INDICES (Detailed is true)TABLESREL_LISTING, INDICES_LISTING, COLUMNS_LISTING, TABLE_COMMENT_LISTING, DDL_LISTINGCOLUMNS_LISTINGCOLUMNS (Detailed is false)REL_LISTINGREL (Detailed is false)INDICES_LISTINGINDICES (Detailed is false)

The root of the tree is the main dictionary. Additional dictionaries are then loaded from the root to form the dictionary tree

If a template has no sections in it, then any variables used in the template will be looked up in the main dictionary. If a variable is not found in the main dictionary (which can be thought of as associated with the default, or main, section) then no data will be generated in the output file for that marker

Evaluation of variables

The tree structure of the data dictionaries is important when it comes to evaluation of variables. As variables are defined in data dictionaries, their associated value only has meaning when that particular data dictionary is active, and that means when the section associated with that data dictionary is active. When a variable lookup occurs, the system will check the data dictionary associated with the current section. If the variable value can be found there the replacement is made. However, if the variable's value is not found in the current data dictionary then the parent data dictionary will be checked for the variable's value and so on up the tree until the main data dictionary, or root, is reached

This can best be illustrated by an example. Assume we want to display the names of all columns in a model. Consider the following template as an attempt to achieve this

    Report
    ------
    Column Name: {{COLUMN_NAME}}
  

This template will produce no output, even for a model that contains many columns. In this example the only data dictionary active is the main dictionary.

Schema: Airlines
Schema: Airports

Schema: Airlines
Schema: Airports

Schema: Airlines
Schema: Airports

With this knowledge the template can be improved as follows

    Report
    ------
    {{#COLUMNS}}
    Column Name: {{COLUMN_NAME}}
    {{/COLUMNS}}
  

This still does not produce output. Referring to the table explains why. Kamus data ________28______39 memiliki kamus induk

Schema: Airlines
Schema: Airports

Schema: Airlines
Schema: Airports

Schema: Airlines
Schema: Airports

Schema: Airlines
Schema: Airports

So to achieve the desired output we would need the template to be something like the following

    Report
    ------

    {{#SCHEMATA}}
    {{#TABLES}}
    {{#COLUMNS_LISTING}}
    {{#COLUMNS}}
    Column Name: {{COLUMN_NAME}}
    {{/COLUMNS}}
    {{/COLUMNS_LISTING}}
    {{/TABLES}}
    {{/SCHEMATA}}

  

The following template is the same, but with explanatory comments added

    Report
    ------

    {{! Main dictionary active}}
    {{#SCHEMATA}}  {{! SCHEMATA dictionary active}}
    {{#TABLES}}  {{! TABLES dictionary active}}
    {{#COLUMNS_LISTING}} {{! COLUMNS_LISTING dictionary active}}
    {{#COLUMNS}}  {{! COLUMNS dictionary active}}
    Column Name: {{COLUMN_NAME}} {{! COLUMN_NAME variable is looked-up, and found, in COLUMNS data dictionary}}
    {{/COLUMNS}}
    {{/COLUMNS_LISTING}}
    {{/TABLES}}
    {{/SCHEMATA}}

  

Imagine now that for each column name displayed you also wanted to display its corresponding schema name, the template would look like this

    Report
    ------

    {{#SCHEMATA}}
    {{#TABLES}}
    {{#COLUMNS_LISTING}}
    {{#COLUMNS}}
    Schema Name: {{SCHEMA_NAME}} Column Name: {{COLUMN_NAME}}
    {{/COLUMNS}}
    {{/COLUMNS_LISTING}}
    {{/TABLES}}
    {{/SCHEMATA}}

  

When variable lookup is performed for

Schema: Airlines
Schema: Airports

Schema: Airlines
Schema: Airports

Schema: Airlines
Schema: Airports

Schema: Airlines
Schema: Airports

If there are multiple schemata in the model the outer section will be iterated over a matching number of times, and

Schema: Airlines
Schema: Airports

It's important to always consider which dictionary needs to be active (and which parents) for a variable to be evaluated correctly. In the following section you will find a table that helps you identify section requirements

7. 11. 1. Supported Template Markers

A list of supported markers follows. These markers can be used in any template, including custom templates

Marker textTypeData Dictionary defined in (if variable) or parent dictionary (if section)Corresponding dataTITLEVariableMAINTitle of the reportGENERATEDVariableMAINDate and time that the report was generatedSTYLE_NAMEVariableMAINThe name of the style selected in MySQL Workbench. This is typically used to load the corresponding CSS file, depending on the name of the style selected in MySQL Workbench. SCHEMA_COUNTVariableMAINThe total number of schemata in the modelPROJECT_TITLEVariableMAINPROJECT_NAMEVariableMAINPROJECT_AUTHORVariableMAINPROJECT_VERSIONVariableMAINPROJECT_DESCRIPTIONVariableMAINPROJECT_CREATEDVariableMAINPROJECT_CHANGEDVariableMAINTOTAL_TABLE_COUNTVariableMAINTotal number of tables in all schemata contained in the model. TOTAL_COLUMN_COUNTVariableMAINTotal number of columns in all tables in all schemata in the model. TOTAL_INDEX_COUNTVariableMAINTotal number of indexes in the model. TOTAL_FK_COUNTVariableMAINTotal number of foreign keys in the model. SCHEMATASectionMAINUsed to mark the start and end of a SCHEMATA section. The SCHEMATA data dictionary becomes active in this section. SCHEMA_NAMEVariableSCHEMATAThe name of a schema in the modelSCHEMA_IDVariableSCHEMATAThe ID of the schemaTABLE_COUNTVariableSCHEMATATotal total number of tables in the current schemaCOLUMN_COUNTVariableSCHEMATAThe total number of columns in the current schemaINDICES_COUNTVariableSCHEMATAThe total number of indexes in the current schemaFOREIGN_KEYS_COUNTVariableSCHEMATAThe total number of foreign keys in the current schemaTABLESSectionSCHEMATAMarks the start and end of a TABLES section. The TABLES data dictionary becomes active in this section. TABLE_NAMEVariableTABLESThe table nameTABLE_IDVariableTABLESThe table IDCOLUMNS_LISTINGSectionTABLESMarks the start and end of a COLUMNS_LISTING section. The COLUMNS_LISTING data dictionary becomes active in this section. COLUMNSSectionCOLUMNS_LISTINGMarks the start and end of a COLUMNS section. The COLUMNS data dictionary becomes active in this section. COLUMN_KEYVariableCOLUMNSWhether the column is a primary key or notCOLUMN_NAMEVariableCOLUMNSThe name of the columnCOLUMN_DATATYPEVariableCOLUMNSThe data type of the columnCOLUMN_NOTNULLVariableCOLUMNSWhether or not the column allows NULLsCOLUMN_DEFAULTVALUEVariableCOLUMNSThe default value of entries in this columnCOLUMN_COMMENTVariableCOLUMNSAny comment for this columnCOLUMN_IDVariableCOLUMNSThe ID of the columnCOLUMN_KEY_PARTVariableCOLUMNS (if detailed)The type of column keyCOLUMN_NULLABLEVariableCOLUMNS (if detailed)Can the column contain NULLsCOLUMN_AUTO_INCVariableCOLUMNS (if detailed)Does the column auto-incrementCOLUMN_CHARSETVariableCOLUMNS (if detailed)The character set used by the columnCOLUMN_COLLATIONVariableCOLUMNS (if detailed)The collation used by the columnCOLUMN_IS_USERTYPEVariableCOLUMNS (if detailed)Whether or not the column is a user typeINDICES_LISTINGSectionTABLESMarks the start and end of an INDICES_LISTING section. The INDICES_LISTING data dictionary becomes active in this section. INDICESSectionINDICES_LISTINGMarks the start and end of an INDICES section. The INDICES data dictionary becomes active in this section. INDEX_NAMEVariableINDICESThe name of the indexINDEX_PRIMARYVariableINDICESIs this a primary indexINDEX_UNIQUEVariableINDICESIs this a unique indexINDEX_TYPEVariableINDICESThe type of index e. g. PRIMARYINDEX_KINDVariableINDICESThe kind of indexINDEX_COMMENTVariableINDICESA comment for the indexINDEX_IDVariableINDICESThe ID of the indexINDEX_COLUMNSSectionINDICESMarks the start and end of an INDEX_COLUMNS section. The INDEX_COLUMNS data dictionary becomes active in this section. INDEX_COLUMN_NAMEVariableINDEX_COLUMNSThe index column nameINDEX_COLUMN_ORDERVariableINDEX_COLUMNSThe index column order e. g. ascending, descendingINDEX_COLUMN_COMMENTVariableINDEX_COLUMNSA comment for the index columnINDEX_KEY_BLOCK_SIZEVariableINDEX_COLUMNS (if detailed)Index key block sizeREL_LISTINGSectionTABLESMarks the start and end of a REL_LISTING section. The REL_LISTING data dictionary becomes active in this section. RELSectionREL_LISTINGMarks the start and end of a REL section. The REL data dictionary becomes active in this section. REL_NAMEVariableREL, FOREIGN_KEYSRelationship nameREL_TYPEVariableREL, FOREIGN_KEYSRelationship typeREL_PARENTTABLEVariableREL, FOREIGN_KEYSParent table of relationshipREL_CHILDTABLEVariableREL, FOREIGN_KEYSChild table of relationshipREL_CARDVariableREL, FOREIGN_KEYSRelationship cardFOREIGN_KEY_IDVariableRELForeign key IDFOREIGN_KEYSSectionSCHEMATAMarks the start and end of a FOREIGN_KEYS section. The FOREIGN_KEYS data dictionary becomes active in this section. FK_DELETE_RULEVariableFOREIGN_KEYSForeign key delete ruleFK_UPDATE_RULEVariableFOREIGN_KEYSForeign key update ruleFK_MANDATORYVariableFOREIGN_KEYSForeign key mandatoryTABLE_COMMENT_LISTINGSectionTABLESMarks the start and end of a TABLE_COMMENT_LISTING section. The TABLE_COMMENT_LISTING data dictionary becomes active in this section. TABLE_COMMENTVariableTABLE_COMMENT_LISTINGA comment for the tableDDL_LISTINGSectionTABLESMarks the start and end of a DDL_LISTING section. The DDL_LISTING data dictionary becomes active in this section. DDL_SCRIPTVariableDDL_LISTINGDisplay the DDL script of the currently active entity e. g. SCHEMATA, TABLES

Using the table

The table shows which variables are defined in which sections. The variable should be used in its correct section, otherwise its value will not be displayed

It should be remembered though that the data dictionaries used to perform the lookup form a hierarchical tree, so it is possible to use a variable defined in a parent section, in a child section

7. 11. 2. Creating a custom template

In the simplest case a template consists of two files. A template file, which has a

Schema: Airlines
Schema: Airports

Schema: Airlines
Schema: Airports

Schema: Airlines
Schema: Airports

One of the easiest ways to create a custom template is to make a copy of any existing template

For example, you make a custom template based on the

Schema: Airlines
Schema: Airports

1. First you need to make a copy of the template on which you are going to base your custom template. Untuk melakukan ini navigasikan ke folder tempat template disimpan. Dengan asumsi MySQL Workbench telah diinstal ke lokasi default di Windows, ini akan menjadi

   Schema: Airlines
   Schema: Airports

   55

2. Kemudian buat salinan folder template yang Anda inginkan sebagai dasar template baru Anda. Dalam hal ini salinan folder

   Schema: Airlines
   Schema: Airports

   _56 dibuat. Salinan dapat diberi nama yang sesuai, misalnya,

   Schema: Airlines
   Schema: Airports

   57

3. Sekarang file

   Schema: Airlines
   Schema: Airports

   _52 perlu diedit, untuk mencerminkan template khusus Anda. File yang belum diedit dalam hal ini ditampilkan di sini

   Total number of Schemata: {{SCHEMA_COUNT}}

   0

   Dua objek didefinisikan dalam file. Objek

   Schema: Airlines
   Schema: Airports

   _59 dan objek

   Schema: Airlines
   Schema: Airports

   60. Objek ini berisi informasi tentang template yang akan ditampilkan di layar utama wizard Pelaporan Model DBDoc

4. Hal pertama yang perlu Anda ubah adalah GUID objek yang digunakan dalam file. Dalam contoh ini ada dua yang perlu diganti

   Total number of Schemata: {{SCHEMA_COUNT}}

   _1

   Hasilkan dua GUID baru. Ini dapat dilakukan dengan menggunakan alat baris perintah yang sesuai. Ada juga alat online gratis yang dapat digunakan untuk menghasilkan GUID. File

   Schema: Airlines
   Schema: Airports

   _52 kemudian harus diedit sesuai kebutuhan

5. Edit informasi tekstual untuk objek

   Schema: Airlines
   Schema: Airports

   59 dan

   Schema: Airlines
   Schema: Airports

   60 untuk mencerminkan tujuan dari template kustom

6. File yang dimodifikasi sekarang akan terlihat seperti berikut

   Total number of Schemata: {{SCHEMA_COUNT}}

   2

7. The next step is to create the new template file. Again this may best be achieved, depending on your requirements, by editing an existing template. In this example the template file

   Schema: Airlines
   Schema: Airports

   64 is shown here

   Total number of Schemata: {{SCHEMA_COUNT}}

   3

   This template shows details for all schemata in the model

8. The above template file can be edited in any way you like, with new markers being added, and existing markers being removed as required. For the custom template example you might want to create a much simpler template. Such as the one following

   Total number of Schemata: {{SCHEMA_COUNT}}

   4

   This simplified report just lists the schemata and the tables in a model. Tanggal dan waktu pembuatan laporan juga akan ditampilkan sebagai hasil dari penggunaan variabel

   Schema: Airlines
   Schema: Airports

   65

   What data model is MySQL?

   Together, we'll focus on how to model data into relational tables because MySQL is a relational database .

   Is MySQL a relational data model?

   MySQL is the most widely adopted open source relational database and serves as the primary relational data store for many popular websites, applications, and commercial products.

   What are the 4 types of database models?

   Types of database models Hierarchical database model . Relational model. Network model. Object-oriented database model.