Jump to content

Recommended Posts

Posted

Hello everyone! I searched over the net and I found some usefull SQL Commands that a developer (and not only) will need ;)

 

ABORT -- abort the current transaction

ALTER DATABASE -- change a database

ALTER GROUP -- add users to a group or remove users from a group

ALTER TABLE -- change the definition of a table

ALTER TRIGGER -- change the definition of a trigger

ALTER USER -- change a database user account

ANALYZE -- collect statistics about a database

BEGIN -- start a transaction block

CHECKPOINT -- force a transaction log checkpoint

CLOSE -- close a cursor

CLUSTER -- cluster a table according to an index

COMMENT -- define or change the comment of an object

COMMIT -- commit the current transaction

COPY -- copy data between files and tables

CREATE AGGREGATE -- define a new aggregate function

CREATE CAST -- define a user-defined cast

CREATE CONSTRAINT TRIGGER -- define a new constraint trigger

CREATE CONVERSION -- define a user-defined conversion

CREATE DATABASE -- create a new database

CREATE DOMAIN -- define a new domain

CREATE FUNCTION -- define a new function

CREATE GROUP -- define a new user group

CREATE INDEX -- define a new index

CREATE LANGUAGE -- define a new procedural language

CREATE OPERATOR -- define a new operator

CREATE OPERATOR CLASS -- define a new operator class for indexes

CREATE RULE -- define a new rewrite rule

CREATE SCHEMA -- define a new schema

CREATE SEQUENCE -- define a new sequence generator

CREATE TABLE -- define a new table

CREATE TABLE AS -- create a new table from the results of a query

CREATE TRIGGER -- define a new trigger

CREATE TYPE -- define a new data type

CREATE USER -- define a new database user account

CREATE VIEW -- define a new view

DEALLOCATE -- remove a prepared query

DECLARE -- define a cursor

DELETE -- delete rows of a table

DROP AGGREGATE -- remove a user-defined aggregate function

DROP CAST -- remove a user-defined cast

DROP CONVERSION -- remove a user-defined conversion

DROP DATABASE -- remove a database

DROP DOMAIN -- remove a user-defined domain

DROP FUNCTION -- remove a user-defined function

DROP GROUP -- remove a user group

DROP INDEX -- remove an index

DROP LANGUAGE -- remove a user-defined procedural language

DROP OPERATOR -- remove a user-defined operator

DROP OPERATOR CLASS -- remove a user-defined operator class

DROP RULE -- remove a rewrite rule

DROP SCHEMA -- remove a schema

DROP SEQUENCE -- remove a sequence

DROP TABLE -- remove a table

DROP TRIGGER -- remove a trigger

DROP TYPE -- remove a user-defined data type

DROP USER -- remove a database user account

DROP VIEW -- remove a view

END -- commit the current transaction

EXECUTE -- execute a prepared query

EXPLAIN -- show the execution plan of a statement

FETCH -- retrieve rows from a table using a cursor

GRANT -- define access privileges

INSERT -- create new rows in a table

LISTEN -- listen for a notification

LOAD -- load or reload a shared library file

LOCK -- explicitly lock a table

MOVE -- position a cursor on a specified row of a table

NOTIFY -- generate a notification

PREPARE -- create a prepared query

REINDEX -- rebuild corrupted indexes

RESET -- restore the value of a run-time parameter to a default value

REVOKE -- remove access privileges

ROLLBACK -- abort the current transaction

SELECT -- retrieve rows from a table or view

SELECT INTO -- create a new table from the results of a query

SET -- change a run-time parameter

SET CONSTRAINTS -- set the constraint mode of the current transaction

SET SESSION AUTHORIZATION -- set the session user identifier and the current user identifier of the current session

SET TRANSACTION -- set the characteristics of the current transaction

SHOW -- show the value of a run-time parameter

START TRANSACTION -- start a transaction block

TRUNCATE -- empty a table

UNLISTEN -- stop listening for a notification

UPDATE -- update rows of a table

VACUUM -- garbage-collect and optionally analyze a database

Posted

this is not a good "guide". Giving the queries is just too lame. You need to inform the user how to use them and what else does he/she need. This explains what I mean...that from my side. Do not take it as bad words.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Posts

    • ## SuperPoint Editor   SuperPoint Editor is a practical visual editor for Lineage II PTS 'SuperPoint.bin' files. It is built for people who need to inspect, fix, rebuild, and draw server routes without digging through binary data by hand.   ### What You Can Do   - Open and edit 'SuperPoint.bin' files. - Export BIN data into a readable TXT format. - Save edited data back into a valid BIN file. - Validate routes before saving. - Work with SuperPoint routes, points, directed connections, and path records in tables. - Add, duplicate, delete, and reorder points. - Create direct and reverse connections between route points. - Automatically generate connections between neighboring points. - Edit raw point coordinates: 'X', 'Y', 'Z', 'Index', and 'Delay'. - Keep route names and internal route data organized. - Use either English or Ukrainian interface language.   ### C4 Server Support   Some C4 servers have 'SuperPoint.bin', but do not have 'superpointinfo.txt' in scripts. The editor supports this case directly. When 'superpointinfo.txt' is not found near the BIN file, the editor can open the BIN in C4 mode. In this mode, 'Fstring ID' is disabled because that value belongs to 'superpointinfo.txt', not to the BIN itself. The editor will not generate or modify 'superpointinfo.txt' while working in this mode. This keeps C4 data clean and avoids creating script files that the server does not actually use.   ### superpointinfo.txt Support   For chronicles that do use 'superpointinfo.txt', the editor can load and synchronize it together with the BIN data. When saving, the editor updates route nodes and coordinates while preserving existing metadata such as: - 'npc_name' - 'move_type' - 'fstring_index' - 'social_number' - 'delay' New nodes are generated with safe default values, so existing script metadata is not accidentally wiped.   ### Geodata Tools   The editor can also open converted geodata '.dat' files and display them as a map. This makes route editing much more visual. You can: - Load geodata and inspect the terrain by layer. - Zoom and pan around the map. - Create a new SuperPoint directly from a map cell. - Draw a route by clicking on the geodata. - Drag existing points to new positions. - Automatically snap 'X/Y' to the selected geo cell. - Use the selected geodata layer to fill the point 'Z'. - See all routes on the map or focus only on the selected one. This is especially useful when building new NPC movement paths or correcting bad route coordinates.   ### Connections and Paths   SuperPoint connections are directional. A connection from point '3' to point '2' is not the same as a connection from point '2' to point '3'. The editor makes this explicit by separating: - route points, - directed connections, - and the actual path records used by each connection. For simple cases, it can create direct path records automatically. For more complex movement, you can edit the path points manually. ### Built for Safe Editing The editor includes validation before saving, so common structural problems can be caught before a broken BIN is produced. It also verifies rebuilt BIN files through the converter engine. The goal is simple: edit quickly, but do not silently damage server data.   ### Unknown Field   This small 'Unknown' field is part of the original BIN structure. Most official-looking files keep it as '0', and for regular route editing there is usually no reason to change it. The editor exposes it so nothing from the BIN is hidden or lost. If you do not know exactly what your server uses it for, keep it at '0'. Download
    • NpcGrp não salva no interlúdio e da crítico quando coloca ele no cliente, já testei ele antes.
  • Topics

×
×
  • Create New...

Important Information

This community uses essential cookies to function properly. Non-essential cookies and third-party services are used only with your consent. Read our Privacy Policy and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..