Contacts     ->      ICQ:    699 512 265,         E-Mail: CerebroSQL@gmail.com

  • YouTube Social  Icon

SQL Query Editor

Query Editor window is logically divided into 4 blocks:

  • Department sheets (№1)

    • Creating a sheet to work with Oracle databases

    • Creating a sheet to work with SQLite databases

    • Creating a sheet to work with PostgreSQL database

    • Creating a sheet to work with MySQL database

  • Removing akivnogo sheet

    • Connecting to a database / object tree / wood sheets (№2)

    • Group "Connect" [Database Connection]

    • Group "Objects" [The object tree DB]

    • Group "Tabs" [Tree of sheets to quickly jump]

  • Area worksheets (№3)

  • Statistics "Nuclei Monitoring" / "query" (№4)

 

Total:
When working with all types of database editor uses a single syntax for queries.

When you perform a single query (select), it may end with the ';' (semicolon).
When you create designs it should not end with the ';' (Semicolon), if it does not require the presence of the command syntax.

For example:
The design "create user ..." does not require a character at the end of the command, with the "create procedure ..." requires his presence!

When you run scripts: To separate commands from one another symbol is used as a separator ';' for all teams except the team and create the declare, after must go '/' character

An example of the correct syntax:
-----------------------------------------------
show_rep;
create table db.cer_tst (n int)
/
insert into db.cer_tst values ​​(1);
print_on;
select * from db.cer_tst;
drop table db.cer_tst;
-----------------------------------------------

Hints editor (version 3.7 and above)

  • cStr ('') - Add a comment

  • Example cStr ('instance name')

  • delim ('') - to add a row delimiter in the output window

  • print_off - disable the output in the Output window

  • print_on - enable data output to the Output window

  • rdelim_off - disable this column separator

  • rdelim_on - include the output column separator

  • show_rep - show report

  • snum_off - disable numeryatsiyu rows in the report

  • snum_on - include line numbers in the report

Query Editor [Oracle] >>>
Query Editor [PostgreSQL] >>>
Query Editor [MySQL] >>>

Query Editor [SQLite] >>>