You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+79-12Lines changed: 79 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -53,48 +53,115 @@ pip3 install openPanthera
53
53
python3 -m openPanthera.menu
54
54
```
55
55
56
+
## How does it work?
56
57
57
-
# Controll and comands.
58
+
The Panthera currently has 12 different directories, each represent one type of SQL scripts.
59
+
These scripts and migrations are accessed or controlled through the menu and the CLI interface using commands.
60
+
It's important to note that Panthera does not manage the server itself; that needs to be done separately.
58
61
59
62
60
-
The open Panthera has two control interfaces.
61
-
Command line interface ``` python3 -m openPanthera.cli ``` , and menu interface ```python3 -m openPanthera.menu``` .
62
-
Both interface has the same commands.
63
-
Every command is built from two words.
64
-
Module and function. Every command has a shorter method. The short method is two characters.
63
+
## Controll and comands.
65
64
66
-
# Modules
65
+
The open Panthera has two control interfaces:
66
+
1. the command line interface ``` python3 -m openPanthera.cli ```
67
+
1. the menu interface. ```python3 -m openPanthera.menu``` .
68
+
Both interfaces have the same commands.
69
+
The Panthera interface is a simple command interface, but this may change in the future.
70
+
If it does change, the menu should be renamed to "com," and a real menu interface will be implemented.
71
+
Every command consists of two words: the module and the type. Additionally, every command has a shorter method, which is represented by two characters.
67
72
73
+
## Modules
68
74
69
-
## show or s.
75
+
76
+
### show or s.
70
77
71
78
Show system or database information.
72
79
73
80
74
-
## directory or d.
81
+
###directory or d.
75
82
76
83
All directory tree-related commands belong to this module.
77
84
78
85
79
-
## build or b.
86
+
###build or b.
80
87
81
88
82
89
Build command. This runs the build scripts. However, some build functions execute functions that belong to different modules.
83
90
For example bc. Call a destroy before building everything again.
84
91
85
92
86
-
## x
93
+
###x
87
94
88
95
This is a destructive module.
89
96
Every destroy function belongs to that module.
90
97
91
98
92
99
93
-
## migration or m
100
+
###migration or m
94
101
95
102
This is a data migration module has two functions backup and restore.
96
103
97
104
105
+
##Types.
106
+
In our system, there are 20 different types. Among them, there are 12 script types, and 8 virtual types.
107
+
Some types are combinations of different categories, while others can represent multiple types from various modules,
108
+
not just their parent module. Additionally, there are virtual types that may not be fully related to their function or only partially related to it.
109
+
110
+
111
+
### table or t
112
+
113
+
Represent the ```10-table``` directory. Storing the main tables definition. At the moment the openPantera only supports build.
114
+
115
+
116
+
### link or l
117
+
118
+
Represent the ```15-table-link``` directory. Storing the link tables, most of the time many too many connection representations. At the moment the openPantera only supports build.
119
+
120
+
121
+
### function or f
122
+
123
+
Represent the ```20-function``` directory. Storing the definition of the functions. Panthera only lets you access stored functions and procedures. At the moment the openPantera only supports build. But in the j module implementation is planned.
124
+
125
+
126
+
### procedure or p
127
+
128
+
Represent the ```30-procedure``` directory. Storing the procedure of the definitions. Panthera only lets you access stored functions and procedures. At the moment the openPantera only supports build. But in the j module implementation is planned.
129
+
130
+
131
+
### view or v
132
+
133
+
Represent the ```40-view``` directory. Storing the view of the definitions. It's a good practice to build view tables for the foreign keys. That way they can call in multiple functions and procedures with less pain. Do not forget the Panthera is designed for TDD so the test has to be in place or that makes the system too fragile. At the moment the openPantera only supports build. But in the j module implementation is planned.
134
+
135
+
136
+
### index or i
137
+
138
+
Represent the ```50-index``` directory. Not supported in openPanthera at the moment.
139
+
140
+
141
+
### foreign or f
142
+
143
+
Represent the ```60-foreign``` directory. Storing the foreign key definitions. At the moment the openPantera only supports build. The j module support never be implemented in the openPanthera, because increase the chance of human error.
144
+
145
+
146
+
### migration
147
+
148
+
Represent the ```70-migration``` directory. Migration support scripts. Not supported in openPanthera at the moment.
149
+
150
+
151
+
### seed or s
152
+
153
+
Represent the ```80-seed``` directory. Not supported in openPanthera at the moment.
154
+
155
+
156
+
### event or e
157
+
158
+
Represent the ```90-event``` directory. Not supported in openPanthera at the moment.
159
+
160
+
161
+
### init or i
162
+
163
+
This triggers the initializations. Initializing the Panthera basic table or the directory trees.
0 commit comments