BBS design based on mysql (4)_PHP tutorial

5. Layout module design
The so-called classification is more for the telnet server. In cq66 mode, users can
classify according to their own wishes. Anyway, in the end, access is directly based on the version. .
For access to layout articles, the entire article is used as a parameter when storing. The chunking of the article is completed by this layer
. If the upper layer transmits it in units of blocks, it will be transmitted completely in the upper layer. After combining, it will be transmitted again. Refer to the decomposition of
in this layer; when reading, this layer is accessed in block units. If the upper layer wants to access
in full-text units, the merge work is done in the upper layer, regardless of this layer.
As for whether to create an independent index without affecting the upper-layer operations, it is mainly related to the lower-layer database structure
and mainly considers feasibility, efficiency requirements, etc.
Where to check permissions? Let’s put it on the upper layer. In fact, on the telnet server side,
and cq66 clients will not display special command menus to ordinary users at all. Of course, users can
directly send cq66 commands, and the server side still To check. But you should check it again
without using the function module layer below it. Class BoardManage {
private:

public:
// Classification-related operations
int GetClassNameInfo( int maxclass, char **classid,
char ** classname );
Returns the classified information, Chinese and English names.
int GetBoardName( int maxboards, char *classid,
char **boardname );
Returns the board information in a certain category, general category, select directly..
from sboard
where boardclass == .... For special categories, check the corresponding table. . . .

// Modification requires privileges above the forum administrator
int NewClass( char * newclassname, int type );
Create a new category, a normal category or a special category,
int DeleteClass( char * newclassname );
Delete the classification, but not cascade, that is, this layer is not responsible for consistency, and the upper layer is responsible for changing the classification information of the corresponding layout of
to something else. To rename a category, delete it first and then create it.
int AddClassBoard( const char *classname, char *newboardname);
Add the already created board to a certain category, specifically for special categories. For general categories,
The effect is the same as modifyboardinfo,
int DeleteClassBoard( const char *classname, char *boardname);
Deleting a certain version from a category is also for special categories, and for general categories, the effect is also
is the same as modifyboardinfo , the category attribute of a version can be empty, that is, it does not belong to any category.

// Operations related to version information.
int NewBoard( const char *boardid, char *boardname);
Create a new board and create a corresponding table. Other parameters take default values.
int DeleteBoard( const char *boardid);
Delete a board and delete the corresponding table.
int GetBoardInfo( const char *boardid, char *boardname,
int& numposts, char *masters, char *class,
long &level);
Get the board information.
int ModifyBoardId( const char *oldid, char *newid);
To change the English id, the name of the corresponding table should also be changed,
int ModifyBoardInfo( const char *boardid, char *boardname,
int numposts, char *masters, char *class,
long level );
Modifying layout information requires privileges.

// Operations related to layout articles.
int AddText( char *boardid, char *title, char *writer,
char *text );
Add an article to the layout and internally divide the long article into 2k blocks.
int DeleteText(char *boardid, int num);
Deleting an article just makes a mark and does not modify the corresponding table immediately.
int FlushTable( char *boardid );
Refresh the layout and delete the corresponding records of the deleted articles.
int MarkText(char *boardid, int num, char mark);
Mark the article.
int ModifyTitle( char *boardid, int num, char *newtitle );
Modify the title of the article.
int ModifyText(char *boardid, int num, char *newtext);
Modifying the content of the article does not require privileges for your own article.
int GetTextInfo( const char *boardid, int num, char *title,
char *writer, char& mark);
Get the title information of the article.
int GetText( const char *boardid, int num, int block,
char *text );
Read the content of the article, in blocks.

// Query articles and authors
// Return all query results at once?
int QueryWriter( const char *boardid, char *writer,
char **result);
Query the articles of a certain author on the page.
int QueryTitle( const char *boardid, char *title,
char **result);
Query articles on the layout whose titles contain the specified content.
}
Parameter passing is a rather annoying thing. From an abstract point of view, we hope that the returned data has nothing to do with the
bottom layer, so it should be processed, but from an efficiency point of view, we do not want the data to be transferred Multiple
copies. On the other hand, should the application for space release be completed in the upper layer or in this layer
? If you are not careful, it is easy to have memory errors.