modules
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| modules [2025/01/31 11:15] – created gloria | modules [2025/03/10 07:08] (current) – gloria | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ^ Name ^ Type ^ Comments | + | ====== Introduction: |
| - | | id | Primary | + | |
| - | | clientid | + | |
| - | | modulename | + | The Modules table is used to store information about different modules available in the system. Each entry represents a module, including its unique identifier, associated client, hierarchy, appearance, and status. This table plays a crucial role in organizing and managing modules in the system, ensuring that they are displayed and function correctly in both the backend and front-end application. |
| - | | parentmoduleid | + | |
| - | | defaultmodule | + | |
| - | | dependentmodules | + | ^**Sr. No.** ^ **Name** ^ **Type** |
| - | | ord | int | The order in which the module should appear, typically used for sorting modules. | + | |1| **id** | Primary |
| - | | modulelogo | + | |2| **clientid** |
| - | | appiconname | + | |3| **modulename** | varchar(50) |
| - | | status | + | |4| **parentmoduleid** | int | ID of the parent module, if this module is a submodule of another module. |
| + | |5| **defaultmodule** | int | Indicates if this is the default module. 1=default, 0=not default. | ||
| + | |6| **dependentmodules** | varchar(200) | ||
| + | |7| **ord** | int | The order in which the module should appear, typically used for sorting modules. | ||
| + | |8| **modulelogo** | blob | Stores the logo of the module, in binary format (image). | ||
| + | |9| **appiconname** | varchar(250) | ||
| + | |10| **status** | int | Indicates the module' | ||
modules.1738322146.txt.gz · Last modified: 2025/01/31 11:15 by gloria
