CN110888931A - Data display method and device, server, terminal equipment and readable storage medium - Google Patents
Data display method and device, server, terminal equipment and readable storage medium Download PDFInfo
- Publication number
- CN110888931A CN110888931A CN201911047389.4A CN201911047389A CN110888931A CN 110888931 A CN110888931 A CN 110888931A CN 201911047389 A CN201911047389 A CN 201911047389A CN 110888931 A CN110888931 A CN 110888931A
- Authority
- CN
- China
- Prior art keywords
- data
- target
- data type
- displayed
- field
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/26—Visual data mining; Browsing structured data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24564—Applying rules; Deductive queries
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computational Linguistics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the application provides a data display method, a data display device, a server, a terminal device and a readable storage medium, and aims to solve the problem of messy codes generated during data display. The data display method is applied to a server side, and comprises the following steps: receiving a data query request sent by a terminal, wherein the data query request carries identification information of data to be displayed; acquiring the data to be displayed from a database connected with the server according to the identification information; inquiring a target conversion rule file corresponding to the data to be displayed from a plurality of stored conversion rule files according to the identification information; under the condition that the target conversion rule file is inquired, converting the data type of the data to be displayed into the target data type according to the target data type recorded in the target conversion rule file; and returning the data to be displayed after the data type conversion to the terminal so as to display the data to be displayed through the terminal.
Description
Technical Field
The embodiment of the application relates to the technical field of data processing, in particular to a data display method, a data display device, a server, a terminal device and a readable storage medium.
Background
In the field of data processing technology, there is a growing trend to store and manage data by using databases based on various considerations, and to perform corresponding operations on the databases as needed based on the databases in which the data are stored. Taking data query as an example, people can query a data table corresponding to a data table name from a plurality of data tables stored in a database through the data table name, and display data contents included in the data table on a display device. Or people can inquire the data table corresponding to the data table name from a plurality of data tables stored in the database through the data table name and the column name, inquire a column of data corresponding to the column name from a plurality of columns of data included in the data table, and display the data content included in the column of data on the display device.
In the related art, when some databases (for example, Hbase databases) store data, for data of various data types to be stored, the data types need to be uniformly converted into default data types and then stored. In this way, the data stored in the database are all of a uniform data type. However, when data is queried and displayed based on the database, the displayed data usually includes more scrambled content, which affects the user.
Disclosure of Invention
The embodiment of the application provides a data display method, a data display device, a server, a terminal device and a readable storage medium, and aims to solve the problem of messy codes generated during data display.
A first aspect of the embodiments of the present application provides a data display method, which is applied to a server, and the method includes:
receiving a data query request sent by a terminal, wherein the data query request carries identification information of data to be displayed;
acquiring the data to be displayed from a database connected with the server according to the identification information;
inquiring a target conversion rule file corresponding to the data to be displayed from a plurality of stored conversion rule files according to the identification information;
under the condition that the target conversion rule file is inquired, converting the data type of the data to be displayed into the target data type according to the target data type recorded in the target conversion rule file;
and returning the data to be displayed after the data type conversion to the terminal so as to display the data to be displayed through the terminal.
A second aspect of the embodiments of the present application provides a data display method, which is applied to a terminal, and the method includes:
responding to data query operation input by a user, and sending a data query request to a server, wherein the data query request carries identification information of data to be displayed;
receiving data to be displayed returned by the server, wherein the data to be displayed is obtained by the server after acquiring corresponding data from a database connected with the server according to the identification information, inquiring a target conversion rule file corresponding to the data from a plurality of stored conversion rule files according to the identification information, and converting the data type of the data into the target data type according to the target data type recorded in the target conversion rule file;
and displaying the data to be displayed.
A third aspect of the embodiments of the present application provides a data display device, which is applied to a server, where the device includes:
the request receiving module is used for receiving a data query request sent by a terminal, wherein the data query request carries identification information of data to be displayed;
the data acquisition module is used for acquiring the data to be displayed from a database connected with the server according to the identification information;
the file query module is used for querying a target conversion rule file corresponding to the data to be displayed from a plurality of stored conversion rule files according to the identification information;
the data type conversion module is used for converting the data type of the data to be displayed into the target data type according to the target data type recorded in the target conversion rule file under the condition that the target conversion rule file is inquired;
and the data returning module is used for returning the data to be displayed after the data type conversion to the terminal so as to display the data to be displayed through the terminal.
A fourth aspect of the embodiments of the present application provides a data display apparatus, which is applied to a terminal, the apparatus includes:
the request sending module is used for responding to data query operation input by a user and sending a data query request to the server, wherein the data query request carries identification information of data to be displayed;
the data receiving module is used for receiving data to be displayed returned by the server, wherein the data to be displayed is obtained by the server after acquiring corresponding data from a database connected with the server according to the identification information, inquiring a target conversion rule file corresponding to the data from a plurality of stored conversion rule files according to the identification information, and converting the data type of the data into the target data type according to the target data type recorded in the target conversion rule file;
and the data display module is used for displaying the data to be displayed.
A fifth aspect of the embodiments of the present application provides a server, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where when the processor executes the computer program, the server implements the steps of the method according to the first aspect of the present application.
A sixth aspect of the embodiments of the present application provides a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where when the processor executes the computer program, the steps of the method according to the second aspect of the present application are implemented.
A seventh aspect of embodiments of the present application provides a computer-readable storage medium, on which a computer program is stored, which, when executed by a processor, implements the steps in the method according to the first or second aspect of the present application.
The data display method provided by the embodiment of the application is implemented based on interaction between the server and each terminal. The server is connected with the database, or the database is deployed in the server. The database stores a plurality of data, the server stores the conversion rule file of each data or partial data, and the server can inquire and update each conversion rule file.
By adopting the data display method provided by the embodiment of the application, after the server receives the data query request sent by the terminal, the corresponding data to be displayed is obtained from the database according to the identification information carried in the query request, and the corresponding target conversion rule file is queried according to the identification information. And under the condition that the target conversion rule file is inquired, converting the data type of the data to be displayed into the target data type according to the target data type recorded in the target conversion rule file, and returning the data to be displayed after the data type conversion to the terminal for displaying. Therefore, the terminal displays the data to be displayed after the data type conversion, and the possibility of generating messy codes can be effectively reduced.
In addition, when the server side responds to the data query request, the data type conversion is preferentially carried out on the data to be displayed, which is aimed at by the data query request, according to the target data type recorded in the target conversion rule file, so that the scrambling code rate of the data to be displayed can be reduced. Therefore, after the terminal displays the data to be displayed, due to the reduction of the scrambling code rate, the post-processing task amount of the user to the scrambling code can be reduced.
Furthermore, because the data display method provided by the application is implemented based on the interaction between the server and each terminal, the server can respond to the data query requests of a plurality of terminals by using the stored conversion rule file. For example, the server may respond to data query requests for data a from multiple terminals using the conversion rule file a stored by the server. Therefore, the conversion rule file is convenient to manage and update, and once the server side updates the conversion rule file, each terminal device can benefit in time.
It is to be understood that not necessarily all such advantages described above may be achieved in the practice of any one method or product of the embodiments herein.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the description of the embodiments of the present application will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive exercise.
Fig. 1 is a flowchart of a data presentation method according to an embodiment of the present application;
FIG. 2 is a flow chart of a data presentation method according to another embodiment of the present application;
FIG. 3 is a diagram of a transformation rules file according to an embodiment of the present application;
FIG. 4 is a flow chart of a data presentation method according to another embodiment of the present application;
FIG. 5 is a schematic diagram of a terminal user interface according to an embodiment of the present application;
FIG. 6 is a schematic diagram of a data presentation system according to an embodiment of the present application;
FIG. 7 is a schematic view of a data presentation device provided in accordance with an embodiment of the present application;
fig. 8 is a schematic diagram of a data display device according to another embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In the related art, when some databases (for example, Hbase databases) store data, for data of various data types to be stored, the data type needs to be uniformly converted into a default data type (for example, a byte code type), and then the data is stored. In this way, the data stored in the database are all of a uniform data type. When querying and presenting data based on the database, it is common to convert the data read from the database into another default data type (e.g., a string type), and then present the converted data. However, since the original data type of the partial content in the data is not a character string type, the partial content usually appears as a messy code when being displayed, thereby affecting the use of the user.
To solve the problem of generating scrambling codes during data display, referring to fig. 1, fig. 1 is a flowchart of a data display method according to an embodiment of the present application. The method is implemented based on the interaction between the server and each terminal. The server is connected with the database, or the database is deployed in the server. The database stores a plurality of data, the server stores the conversion rule file of each data or partial data, and the server can inquire and update each conversion rule file.
The method shown in fig. 1 is mainly applied to the server side, and as shown in fig. 1, the method includes the following steps:
step S11: and receiving a data query request sent by a terminal, wherein the data query request carries identification information of data to be displayed.
Step S12: and acquiring the data to be displayed from a database connected with the server according to the identification information.
The identification information is used for referring to data to be displayed, and usually one identification information corresponds to a unique piece of data or a group of data. In some embodiments, the identification information of the data to be presented may be a data table name, a row name, or a column name of the data to be presented. Taking the database as the Hbase database as an example, the identification information of the data to be displayed may be a data table name and a row key rowkey of the data to be displayed.
And if the identification information of the data to be displayed is the name of the data table, the acquired data to be displayed is the data table corresponding to the name of the data table. And if the identification information of the data to be displayed is the name and the row key of the data table, the acquired data to be displayed is a row of data corresponding to the row key in the data table corresponding to the name of the data table.
Step S13: and inquiring a target conversion rule file corresponding to the data to be displayed from the stored multiple conversion rule files according to the identification information.
The conversion rule file of one data records a target data type aiming at the data and is used for guiding the server to convert the data type of the data when the server reads the data.
In some embodiments, each conversion rule file has a mapping relationship with the identification information of the corresponding data, and the mapping relationship is also stored in the server. For example, a conversion rule file a corresponds to a data table, the table name of the data table is "a", and the identification information of the data table is also "a", so that a mapping relationship exists between the conversion rule file a and the identification information "a". During the online interaction between the server and the terminal, if the identification information carried in the data query request received by the server is "a", the server can query the conversion rule file a from the multiple conversion rule files according to the identification information.
Step S14: and under the condition that the target conversion rule file is inquired, converting the data type of the data to be displayed into the target data type according to the target data type recorded in the target conversion rule file.
The data type of the data to be displayed refers to: the type of data when the data to be presented is stored in the database. As mentioned above, for example, when some databases store data, for the data of various data types to be stored, the data types need to be uniformly converted into default data types, such as byte code types, and then stored. Therefore, the data type of the data to be displayed read from the database is the byte code type.
Assuming that the target data type recorded in the target conversion rule file of the data to be presented is a floating point type, when step S14 is executed, it is specifically necessary to convert the data type of the data to be presented from a bytecode type to a floating point type.
Step S15: and returning the data to be displayed after the data type conversion to the terminal so as to display the data to be displayed through the terminal.
Therefore, the terminal displays the data to be displayed after the data type conversion, and the possibility of generating messy codes can be effectively reduced. In addition, in the data display method, when the server side responds to the data query request, the data type conversion is preferentially carried out on the data to be displayed, which is aimed at by the data query request, according to the target data type recorded in the target conversion rule file, so that the random code rate of the data to be displayed can be reduced. Therefore, after the terminal displays the data to be displayed, due to the reduction of the scrambling code rate, the post-processing task amount of the user to the scrambling code can be reduced.
In implementing the above method including steps S11 through S15, there are many possible embodiments. For example, one possible embodiment is: the server side stores the respective conversion rule file of each data. The conversion rule file of one data is generated by the server side simultaneously during the period that the server side writes the data into the database.
Illustratively, after the server obtains a copy of data B to be written into the database, the server generates a conversion rule file B for the data B during writing the data B into the database. The generated conversion rule file b does not include the target data type, and the conversion rule file b is updated in the post-processing process of the server, so that the target data type is recorded in the conversion rule file b, and a specific updating mode can be referred to as the following. Or, the original data type of the data B before being written into the database may be recorded in the generated conversion rule file B, and in the post-processing process of the server, the conversion rule file B may be updated to replace the data type, where a specific updating manner may be as follows.
For another example, another possible embodiment is: and a conversion rule file of partial data is stored in the server. The conversion rule file of a piece of data is generated by the server during the period of responding to the data query request after the server stores the piece of data to the database and receives the first data query request aiming at the piece of data. In this way, in some cases, for example, when the server receives a data query request for a certain piece of data for the first time, in response to the data query request, the server cannot query the conversion rule file corresponding to the piece of data when the above step S13 is executed.
To this end, referring to fig. 2, fig. 2 is a flowchart of a data presentation method according to another embodiment of the present application. As shown in fig. 2, the method may further include the steps of:
step S16: and under the condition that the target conversion rule file is not inquired, converting the data type of the data to be displayed into a default data type.
For example, the default data type is usually set as a character string, considering that the probability that the data type of the data to be presented is a character string before the data to be presented is stored in the database is usually high.
As mentioned above, after step S16 is completed, a conversion rule file may be generated for the data to be presented, where the target data type recorded in the conversion rule file is the default data type. In the post-processing process of the server, the conversion rule file is updated so as to replace the default data type, and a specific updating manner can be referred to below.
In addition, as shown in fig. 2, step S16 and step S14 are two parallel steps, and after step S16 is executed, step S15 is executed, so that the data to be displayed after data type conversion is returned to the terminal for displaying.
In the present application, after the above steps S11-S15, or after the above steps S11, S12, S13, S16 and S15, the data displayed by the terminal usually has no scrambling code, so that the problem of scrambling code is improved. In a few cases, however, there is still a possibility of code scrambling, for which reasons include, but are not limited to, the following:
the first reason is as follows: when the service end carries out service processing, a certain data is called, and the data type of the data is changed when the data participates in calculation. And the target data type recorded in the conversion rule file of the piece of data is not updated. In this way, when the server receives the data query request for the data, the data type of the data is still converted according to the target data type recorded in the conversion rule file, and when the terminal displays the data, a messy code may occur.
The second reason is that: as described above, for a certain data to be displayed, if the server does not query the target conversion rule file corresponding to the data to be displayed, the server converts the data type of the data to be displayed into the default data type. If the default data type is not consistent with the data type of the data to be displayed before the data to be displayed is stored in the database, messy codes may occur when the terminal displays the data to be displayed.
In order to further improve the problem that the code messy still exists in a few cases, the server side can update the conversion rule file. Specifically, after the server performs step S15, the server may further perform the following steps:
step S17-1: receiving a specified data type aiming at the data to be displayed, which is sent by a terminal;
step S17-2: converting the data type of the data to be displayed into the specified data type again;
step S17-3: returning the data to be displayed, which is subjected to the data type conversion again, to the terminal so as to display the data to be displayed again through the terminal;
step S17-4: and updating the target conversion rule file according to the specified data type information.
The specified data type sent by the terminal to the server is input to the terminal by the user.
For example, if the data displayed on the terminal (i.e. the data to be displayed) is scrambled after the above step S15 is completed. The terminal may receive user input of a specified data type, such as a single precision floating point type. And the terminal sends the data type information to the server, the server converts the data type of the data to be displayed into a single-precision floating point type again, and replaces the target data type recorded in the target conversion rule file of the data to be displayed with the single-precision floating point type. In addition, the server side returns the data to be displayed, which is subjected to the data type conversion again, to the terminal for displaying.
If the data displayed on the terminal (namely the data to be displayed) is still messy codes. The terminal may continue to receive another specified data type, such as an integer, entered by the user. The terminal sends the data type information to the server, the server converts the data type of the data to be displayed into integer again, and replaces the target data type (single-precision floating point type) recorded in the target conversion rule file of the data to be displayed with integer. In addition, the server side returns the data to be displayed, which is subjected to the data type conversion again, to the terminal for displaying.
Therefore, the server side realizes the updating of the target conversion rule file of the data to be displayed in the interaction process with the terminal. After that, if the server receives a data query request for the file to be displayed sent by another terminal, the server may perform data type conversion on the data to be processed based on the updated target conversion rule file of the data to be displayed, so that the data to be displayed is normally displayed on the another terminal after being returned to the another terminal.
It can be seen that, since the conversion rule file is stored in the server, the conversion rule file is shared by a plurality of terminal devices. And when the server side updates the conversion rule file during the interaction with a certain terminal device, the server side can respond to the data query requests of other terminal devices by using the updated conversion rule file. Therefore, once the server updates the conversion rule file, each terminal device can gain benefits in time.
In this application, in some embodiments, a piece of data to be presented may be a data table, or may be a list of data, the data to be presented includes a plurality of fields, and the target data type recorded in the target conversion rule file of the data to be presented is a target data type for each field. Referring to fig. 3, fig. 3 is a schematic diagram of a transformation rule file according to an embodiment of the present application. As shown in FIG. 3, the conversion rule file includes target data types for a plurality of fields.
Based on the above situation, when the step S14 is executed, the following sub-steps may be specifically executed:
step S14-1: and for each field in the plurality of fields included in the data to be displayed, converting the data type of the field into the target data type corresponding to the field under the condition that the target data type for the field is recorded in the target conversion rule file.
Step S14-2: and for each field in the plurality of fields included in the data to be shown, converting the data type of the field into a default data type under the condition that the target data type for the field is not recorded in the target conversion rule file.
For example, after the server performs the steps S11 to S13, the server acquires the data to be presented from the database, and queries the target conversion rule file corresponding to the data to be presented. And the server side inquires the target data type corresponding to each field of the data to be displayed from the target conversion rule file aiming at each field of the data to be displayed. And if the target data type corresponding to the field is inquired, converting the data type of the field into the target data type. If the target data type corresponding to the field is not inquired, the data type of the field is converted into the default data type, such as a character string type.
Thus, each field in the data to be displayed completes the data type conversion operation, and the server performs the step S15 on the data to be displayed, so that the terminal displays the data to be displayed.
For reasons similar to the first and second reasons, when the terminal device displays the data to be displayed, a small number of fields in the data to be displayed still have the possibility of messy codes. In order to further improve the problem that a few fields still have messy codes, the server can update the conversion rule file. Specifically, after the server performs step S15, the server may further perform the following steps:
step S18-1: receiving a target field sent by the terminal and a first specified data type aiming at the target field, wherein the target field is a field in the data to be displayed, and the target field is displayed as messy codes when being displayed by the terminal;
step S18-2: reconverting the data type of the target field to the first specified data type;
step S18-3: returning the target field subjected to the data type conversion to the terminal again so as to display the target field again through the terminal;
step S18-4: recording the first specified data type as a target data type for the target field in the target conversion rule file.
The target field and the first specified data type which are sent to the server by the terminal are input into the terminal by a user.
For example, if after the step S15 is completed, the field 1 in the data displayed on the terminal (i.e. the data to be displayed) is displayed as a messy code. The terminal may receive a user selection of field 1 and receive a first specified data type, e.g., integer, input by the user. The terminal sends the field 1 and the data type information to the server, and the server converts the data type of the field 1 into integer again; or after the server reads the field 1 from the database again, converting the data type of the field 1 which is read again into an integer. And, in the target conversion rule file of the data to be shown, the integer is recorded as the target data type for the field 1. In addition, the server side returns the field 1 which is subjected to data type conversion again to the terminal for display.
When the first specified data type is recorded as the target data type for the target field, on one hand, if the target data type for the target field is recorded in the target conversion rule file, the target data type is replaced by the first specified data type.
On the other hand, if the target data type for the target field is not recorded in the target conversion rule file, the first specified data type is directly recorded as the target data type for the target field.
Following the above example, when an integer is recorded as a target data type for field 1, if the target data type for field 1 is recorded in the target conversion rule file, the target data type is replaced with the integer. If the target data type for the field 1 is not recorded in the target conversion rule file, the integer is directly recorded as the target data type for the field 1.
In addition, after the server performs the step S18-4, the server may further perform the following steps:
step S18-5: receiving the target field sent again by the terminal, and receiving a second specified data type aiming at the target field sent by the terminal, wherein the target field still displays messy codes when being displayed by the terminal;
step S18-6: reconverting the data type of the target field to the second specified data type;
step S18-7: returning the target field subjected to the data type conversion to the terminal again so as to display the target field again through the terminal;
step S18-8: updating the second specified data type to a target data type for the target field in the target transformation rule file.
Following the above example, if the above steps S18-1 to S18-4 are further performed, the field 1 in the data displayed on the terminal (i.e. the data to be displayed) still appears as a scrambling code. The terminal may continue to receive user selection of field 1 and receive user input of a second specified data type, such as a double precision floating point type. The terminal sends the field 1 and the data type information to the server, and the server converts the data type of the field 1 into a double-precision floating point type again; or after the server reads the field 1 from the database again, converting the data type of the field 1 which is read again into a double-precision floating point type. And the target data type (integer type) recorded in the target conversion rule file of the data to be shown is replaced by a double-precision floating point type. In addition, the server side returns the field 1 which is subjected to data type conversion again to the terminal for display.
Therefore, in the interaction process of the server and the terminal, the target conversion rule file of the data to be displayed is updated, so that the target data type corresponding to the field 1 is updated to be a double-precision floating point type. After that, if the server receives a data query request for the file to be displayed sent by another terminal, the server may perform data type conversion on the data to be processed based on the updated target conversion rule file of the data to be displayed, so that the data to be displayed is normally displayed on the another terminal after being returned to the another terminal.
Based on the same inventive concept, referring to fig. 4, fig. 4 is a flowchart of a data presentation method according to another embodiment of the present application. The method is implemented based on the interaction between the server and each terminal. The server is connected with the database, or the database is arranged in the server. The database stores a plurality of data, the server stores the conversion rule file of each data or partial data, and the server can inquire and update each conversion rule file.
The method shown in fig. 4 is mainly applied to the terminal side, and as shown in fig. 4, the method includes the following steps:
step S41: and responding to the data query operation input by the user, and sending a data query request to the server, wherein the data query request carries the identification information of the data to be displayed.
When receiving a data query operation input by a user, the terminal obtains identification information of data to be displayed, wherein the identification information can be input by the user. The identification information may be entered by a user via an input device such as a keyboard, mouse, microphone, touchpad, touch screen, etc.
Step S42: and receiving data to be displayed returned by the server, wherein the data to be displayed is obtained after the server acquires corresponding data from a database connected with the server according to the identification information, inquires a target conversion rule file corresponding to the data from a plurality of stored conversion rule files according to the identification information, and converts the data type of the data into the target data type according to the target data type recorded in the target conversion rule file.
For example, the processing procedure of the server can be referred to above, and is not described in detail herein.
Step S43: and displaying the data to be displayed.
By executing the method comprising the steps S41 to S43, the terminal displays the data to be displayed after the data type conversion, so that the possibility of generating a messy code can be effectively reduced. In addition, in the data display method, when the server side responds to the data query request, the data type conversion is preferentially carried out on the data to be displayed, which is aimed at by the data query request, according to the target data type recorded in the target conversion rule file, so that the random code rate of the data to be displayed can be reduced. Therefore, after the terminal displays the data to be displayed, due to the reduction of the scrambling code rate, the post-processing task amount of the user to the scrambling code can be reduced.
In this application, in some embodiments, a piece of data to be presented may be a data table, or may be a list of data, the data to be presented includes a plurality of fields, and the target data type recorded in the target conversion rule file of the data to be presented is a target data type for each field.
For reasons similar to the above-mentioned reason one and reason two, when the terminal displays the data to be displayed, a small number of fields in the data still have the possibility of scrambling codes. In order to further improve the problem that a few fields still have messy codes, the conversion rule file can be updated. Specifically, after executing the step S43, the terminal may further execute the following steps:
step S44-1: receiving a selection operation aiming at a target field in the data to be displayed and a first specified data type aiming at the target field, wherein the selection operation is input by a user;
step S44-2: sending the target field and the first specified data type to the server, so as to convert the data type of the target field into the first specified data type again through the server, and recording the first specified data type as the target data type for the target field in the target conversion rule file;
step S44-3: receiving a target field returned by the server and subjected to data type conversion again;
step S44-4: the target field is shown again.
For example, if after the step S43 is completed, the field 2 in the data displayed on the terminal (i.e. the data to be displayed) is displayed as a messy code. The terminal may receive a user selection of field 2 and receive a first specified data type, e.g., integer, input by the user. The terminal sends the field 1 and the data type information to the server, and the server converts the data type of the field 2 into integer again; or after the server reads the field 2 from the database again, the data type of the field 2 which is read again is converted into an integer. And, in the target conversion rule file of the data to be shown, the integer is recorded as the target data type for the field 2. In addition, the server returns the field 2 which is subjected to data type conversion again to the terminal.
And the terminal receives the field 2 returned by the server and subjected to data type conversion again, and displays the field 2. For example, the terminal again presents past field 2 in the data to be presented at the original position of field 2.
In addition, after the terminal performs the step S44-4, the terminal may further perform the following steps:
step S44-5: receiving a selection operation input again by the user and aiming at the target field, and receiving a second specified data type input by the user and aiming at the target field;
step S44-6: sending the target field and the second specified data type to the server, so as to convert the data type of the target field into the second specified data type again through the server, and updating the second specified data type into the target data type for the target field in the target conversion rule file;
step S44-7: receiving a target field returned by the server and subjected to data type conversion again;
step S44-8: the target field is shown again.
Following the above example, if the above steps S44-1 to S44-4 are further performed, the field 2 in the data displayed on the terminal (i.e. the data to be displayed) still appears as garbled code. The terminal may continue to receive user selection of field 2 and receive user input of a second specified data type, such as a double precision floating point type. The terminal sends the field 2 and the data type information to the server, and the server converts the data type of the field 2 into a double-precision floating point type again; or after the server reads the field 2 from the database again, converting the data type of the field 2 which is read again into a double-precision floating point type. And the target data type (integer type) recorded in the target conversion rule file of the data to be shown is replaced by a double-precision floating point type. In addition, the server returns the field 2 which is subjected to data type conversion again to the terminal.
And the terminal receives the field 2 returned by the server and subjected to data type conversion again, and displays the field 2. For example, the terminal again presents through field 2 at the original position of field 2 in the data to be presented.
Therefore, in the interaction process of the server and the terminal, the target conversion rule file of the data to be displayed is updated, so that the target data type corresponding to the field 2 is updated to be a double-precision floating point type. After that, if the server receives a data query request for the file to be displayed sent by another terminal, the server may perform data type conversion on the data to be processed based on the updated target conversion rule file of the data to be displayed, so that the data to be displayed is normally displayed on the another terminal after being returned to the another terminal.
In the present application, a first specified data type for the target field is facilitated for user input. Referring to fig. 5, fig. 5 is a schematic diagram of a terminal user interface according to an embodiment of the present application. As illustrated in fig. 5, the terminal may provide the user with a plurality of graphical selection interfaces 51 for selecting the type of data.
The user, upon entering the specified data type for the selected target field (field filled with gray in fig. 5), may click on one of the graphical selection interfaces to enter the specified data type. And the terminal receives the selection operation of the user on the graphical selection interface and determines the data type corresponding to the selected graphical selection interface as the first specified data type information.
Referring to fig. 6, fig. 6 is a schematic diagram of a data presentation system according to an embodiment of the present application. As shown in fig. 6, the data presentation system mainly includes a terminal, a server, a database, and a cache area. When the system is used, the interaction process is as follows:
(1) the terminal receives data query operation input by a user;
(2) the terminal responds to the data query operation input by the user, and sends a data query request to the server, wherein the data query request carries identification information of data to be displayed (corresponding to the step S41 and the step S11);
(3) the server obtains the data to be displayed from the database connected to the server according to the identification information (corresponding to step S12);
(4) the server side inquires a target conversion rule file corresponding to the data to be displayed from the stored multiple conversion rule files according to the identification information (corresponding to the step S13);
(5) the server converts the data type of the data to be displayed into the target data type according to the target data type recorded in the target conversion rule file (corresponding to the step S14);
(6) the server returns the data to be displayed after the data type conversion to the terminal (corresponding to the step S15 and the step S42);
(7) the terminal displays the data to be displayed (corresponding to the step S43);
(8) the terminal receives a selection operation for a target field in the data to be presented, which is input by a user, and a first specified data type for the target field (corresponding to the step S44-1);
(9) sending the target field and the first specified data type to the server (corresponding to the above step S44-2 and step S18-1);
(10) the server side converts the data type of the target field into the first specified data type again (corresponding to the step 18-2);
(11) the server returns the target field subjected to the data type conversion to the terminal (corresponding to the step 18-3 and the step S44-3);
(12) the server records the first specified data type as a target data type for the target field in the target conversion rule file (corresponding to the step 18-4);
(13) the terminal again presents the object field (corresponding to step S44-3 above).
Based on the same inventive concept, an embodiment of the present application provides a data display device, which is applied to a server. Referring to fig. 7, fig. 7 is a schematic diagram of a data display device according to an embodiment of the present application. As shown in fig. 7, the apparatus includes:
a request receiving module 71, configured to receive a data query request sent by a terminal, where the data query request carries identification information of data to be displayed;
the data acquisition module 72 is configured to acquire the data to be displayed from a database connected to the server according to the identification information;
the file query module 73 is configured to query, according to the identification information, a target conversion rule file corresponding to the data to be displayed from the stored multiple conversion rule files;
a data type conversion module 74, configured to, when the target conversion rule file is queried, convert the data type of the data to be displayed into the target data type according to the target data type recorded in the target conversion rule file;
and a data returning module 75, configured to return the data to be displayed after the data type conversion to the terminal, so as to display the data to be displayed through the terminal.
Optionally, the data to be displayed includes a plurality of fields, and the target data type recorded in the target conversion rule file is a target data type for each field; the data type conversion module comprises:
and the first conversion submodule is used for converting the data type of the field into the target data type corresponding to the field under the condition that the target data type of the field is recorded in the target conversion rule file aiming at each field in a plurality of fields included in the data to be displayed.
Optionally, the data type conversion module further includes:
and the second conversion submodule is used for converting the data type of each field into a default data type under the condition that the target data type of the field is not recorded in the target conversion rule file aiming at each field in the plurality of fields included in the data to be displayed.
Optionally, the apparatus further comprises:
the information receiving module is used for receiving a target field sent by the terminal and a first designated data type aiming at the target field after the data to be displayed after data type conversion is returned to the terminal, wherein the target field is a field in the data to be displayed, and the target field is displayed as messy codes when being displayed by the terminal;
a data type recording module, configured to record the first specified data type as a target data type for the target field in the target conversion rule file;
the data type conversion module is further used for converting the data type of the target field into the first specified data type again;
the data returning module is also used for returning the target field which is subjected to the data type conversion again to the terminal so as to display the target field again through the terminal.
Optionally, the data type recording module includes:
and the data type replacing submodule is used for replacing the target data type with the first specified data type under the condition that the target data type aiming at the target field is recorded in the target conversion rule file.
Optionally, the information receiving module is further configured to, after returning the target field subjected to data type conversion again to the terminal, receive the target field sent again by the terminal, and receive a second specified data type for the target field sent by the terminal, where the target field still displays a messy code when being displayed by the terminal;
the data type conversion module is further used for converting the data type of the target field into the second specified data type again;
the data returning module is also used for returning the target field which is subjected to the data type conversion again to the terminal so as to display the target field again through the terminal;
the data type recording module is further configured to update the second specified data type to a target data type for the target field in the target conversion rule file.
Optionally, the data type conversion module is further configured to, when the target conversion rule file is not queried, convert the data type of the data to be displayed into a default data type.
Based on the same inventive concept, an embodiment of the present application provides another data presentation apparatus, which is applied to a terminal. Referring to fig. 8, fig. 8 is a schematic view of a data display device according to another embodiment of the present application. As shown in fig. 8, the apparatus includes:
the request sending module 81 is configured to send a data query request to the server in response to a data query operation input by a user, where the data query request carries identification information of data to be displayed;
the data receiving module 82 is configured to receive data to be displayed returned by the server, where the data to be displayed is obtained by the server after acquiring corresponding data from a database connected to the server according to the identification information, querying a target conversion rule file corresponding to the data from a plurality of stored conversion rule files according to the identification information, and converting the data type of the data into the target data type according to the target data type recorded in the target conversion rule file;
and the data display module 83 is configured to display the data to be displayed.
Optionally, the data to be displayed includes a plurality of fields, and the target data type information recorded in the target conversion rule file is target data type information for each field; the device further comprises:
the operation receiving module is used for receiving selection operation aiming at a target field in the data to be displayed and a first specified data type aiming at the target field, which are input by a user, after the data to be displayed is displayed;
an information sending module, configured to send the target field and the first specified data type to the server, so as to convert the data type of the target field into the first specified data type again through the server, and record the first specified data type as a target data type for the target field in the target conversion rule file;
the data receiving module is further used for receiving a target field returned by the server and subjected to data type conversion again;
the data display module is further used for displaying the target field again.
Optionally, the operation receiving module is further configured to, after the target field is presented again, receive a selection operation, which is input again by the user, for the target field, and receive a second specified data type, which is input by the user and is for the target field;
the information sending module is further configured to send the target field and the second specified data type to the server, so as to convert the data type of the target field into the second specified data type again through the server, and update the second specified data type to the target data type for the target field in the target conversion rule file;
the data receiving module is further used for receiving a target field returned by the server and subjected to data type conversion again;
the data display module is further used for displaying the target field again.
Optionally, the apparatus further comprises:
the interface providing module is used for providing a plurality of graphical selection interfaces for selecting data types for a user before receiving a first specified data type input by the user and aiming at the target field;
the operation receiving module includes:
the selection operation receiving submodule is used for receiving the selection operation of the user on the graphical selection interface;
and the specified data type determining submodule is used for determining the data type corresponding to the selected graphical selection interface as the first specified data type information.
Based on the same inventive concept, another embodiment of the present application provides a server, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the server implements the steps of the method according to any of the above embodiments applied to the server.
Based on the same inventive concept, another embodiment of the present application provides a terminal device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the method of any of the above embodiments applied to the terminal is implemented.
Based on the same inventive concept, another embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the steps in the method according to any of the above-mentioned embodiments of the present application.
For the device embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, refer to the partial description of the method embodiment.
The embodiments in the present specification are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.
As will be appreciated by one of skill in the art, embodiments of the present application may be provided as a method, apparatus, or computer program product. Accordingly, embodiments of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing terminal to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing terminal to cause a series of operational steps to be performed on the computer or other programmable terminal to produce a computer implemented process such that the instructions which execute on the computer or other programmable terminal provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present application have been described, additional variations and modifications of these embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including the preferred embodiment and all such alterations and modifications as fall within the true scope of the embodiments of the application.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or terminal that comprises the element.
The data display method, the data display device, the server, the terminal device and the readable storage medium provided by the present application are introduced in detail, and a specific example is applied in the text to explain the principle and the implementation of the present application, and the description of the above embodiment is only used to help understanding the method and the core idea of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (16)
1. A data display method is applied to a server side, and the method comprises the following steps:
receiving a data query request sent by a terminal, wherein the data query request carries identification information of data to be displayed;
acquiring the data to be displayed from a database connected with the server according to the identification information;
inquiring a target conversion rule file corresponding to the data to be displayed from a plurality of stored conversion rule files according to the identification information;
under the condition that the target conversion rule file is inquired, converting the data type of the data to be displayed into the target data type according to the target data type recorded in the target conversion rule file;
and returning the data to be displayed after the data type conversion to the terminal so as to display the data to be displayed through the terminal.
2. The method according to claim 1, wherein the data to be presented comprises a plurality of fields, and the target data type recorded in the target conversion rule file is a target data type for each field; the converting the data type of the data to be displayed into the target data type according to the target data type recorded in the target conversion rule file includes:
and for each field in the plurality of fields included in the data to be displayed, converting the data type of the field into the target data type corresponding to the field under the condition that the target data type for the field is recorded in the target conversion rule file.
3. The method of claim 2, further comprising:
and for each field in the plurality of fields included in the data to be shown, converting the data type of the field into a default data type under the condition that the target data type for the field is not recorded in the target conversion rule file.
4. The method according to claim 2 or 3, wherein after the data to be presented after data type conversion is returned to the terminal, the method further comprises:
receiving a target field sent by the terminal and a first specified data type aiming at the target field, wherein the target field is a field in the data to be displayed, and the target field is displayed as messy codes when being displayed by the terminal;
reconverting the data type of the target field to the first specified data type;
returning the target field subjected to the data type conversion to the terminal again so as to display the target field again through the terminal;
recording the first specified data type as a target data type for the target field in the target conversion rule file.
5. The method of claim 4, wherein the recording the first specified data type as a target data type for the target field comprises:
and under the condition that a target data type aiming at the target field is recorded in the target conversion rule file, replacing the target data type by the first specified data type.
6. The method according to claim 4, wherein after returning the destination field that is newly subjected to data type conversion to the terminal, the method further comprises:
receiving the target field sent again by the terminal, and receiving a second specified data type aiming at the target field sent by the terminal, wherein the target field still displays messy codes when being displayed by the terminal;
reconverting the data type of the target field to the second specified data type;
returning the target field subjected to the data type conversion to the terminal again so as to display the target field again through the terminal;
updating the second specified data type to a target data type for the target field in the target transformation rule file.
7. The method of claim 1, further comprising:
and under the condition that the target conversion rule file is not inquired, converting the data type of the data to be displayed into a default data type.
8. A data display method is applied to a terminal, and the method comprises the following steps:
responding to data query operation input by a user, and sending a data query request to a server, wherein the data query request carries identification information of data to be displayed;
receiving data to be displayed returned by the server, wherein the data to be displayed is obtained by the server after acquiring corresponding data from a database connected with the server according to the identification information, inquiring a target conversion rule file corresponding to the data from a plurality of stored conversion rule files according to the identification information, and converting the data type of the data into the target data type according to the target data type recorded in the target conversion rule file;
and displaying the data to be displayed.
9. The method according to claim 8, wherein the data to be presented comprises a plurality of fields, and the target data type information recorded in the target conversion rule file is target data type information for each field; after presenting the data to be presented, the method further comprises:
receiving a selection operation aiming at a target field in the data to be displayed and a first specified data type aiming at the target field, wherein the selection operation is input by a user;
sending the target field and the first specified data type to the server, so as to convert the data type of the target field into the first specified data type again through the server, and recording the first specified data type as the target data type for the target field in the target conversion rule file;
receiving a target field returned by the server and subjected to data type conversion again;
the target field is shown again.
10. The method of claim 9, wherein after re-presenting the target field, the method further comprises:
receiving a selection operation input again by the user and aiming at the target field, and receiving a second specified data type input by the user and aiming at the target field;
sending the target field and the second specified data type to the server, so as to convert the data type of the target field into the second specified data type again through the server, and updating the second specified data type into the target data type for the target field in the target conversion rule file;
receiving a target field returned by the server and subjected to data type conversion again;
the target field is shown again.
11. The method of claim 9 or 10, wherein prior to receiving a user input of a first specified data type for the target field, the method further comprises:
providing a plurality of graphical selection interfaces for selecting data types to a user;
the receiving of the first specified data type input by the user for the target field comprises:
receiving the selection operation of a user on the graphical selection interface;
and determining the data type corresponding to the selected graphical selection interface as the first specified data type information.
12. A data display device is applied to a server side, and the device comprises:
the request receiving module is used for receiving a data query request sent by a terminal, wherein the data query request carries identification information of data to be displayed;
the data acquisition module is used for acquiring the data to be displayed from a database connected with the server according to the identification information;
the file query module is used for querying a target conversion rule file corresponding to the data to be displayed from a plurality of stored conversion rule files according to the identification information;
the data type conversion module is used for converting the data type of the data to be displayed into the target data type according to the target data type recorded in the target conversion rule file under the condition that the target conversion rule file is inquired;
and the data returning module is used for returning the data to be displayed after the data type conversion to the terminal so as to display the data to be displayed through the terminal.
13. A data display device is applied to a terminal, and the device comprises:
the request sending module is used for responding to data query operation input by a user and sending a data query request to the server, wherein the data query request carries identification information of data to be displayed;
the data receiving module is used for receiving data to be displayed returned by the server, wherein the data to be displayed is obtained by the server after acquiring corresponding data from a database connected with the server according to the identification information, inquiring a target conversion rule file corresponding to the data from a plurality of stored conversion rule files according to the identification information, and converting the data type of the data into the target data type according to the target data type recorded in the target conversion rule file;
and the data display module is used for displaying the data to be displayed.
14. A server comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor when executing performs the steps of the method of any one of claims 1 to 7.
15. A terminal device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor when executing performs the steps of the method according to any of claims 8 to 11.
16. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 7 or 8 to 11.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911047389.4A CN110888931B (en) | 2019-10-30 | 2019-10-30 | Data display method and device, server, terminal equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911047389.4A CN110888931B (en) | 2019-10-30 | 2019-10-30 | Data display method and device, server, terminal equipment and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110888931A true CN110888931A (en) | 2020-03-17 |
| CN110888931B CN110888931B (en) | 2022-05-20 |
Family
ID=69746698
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911047389.4A Active CN110888931B (en) | 2019-10-30 | 2019-10-30 | Data display method and device, server, terminal equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110888931B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112269613A (en) * | 2020-10-23 | 2021-01-26 | 北京金和网络股份有限公司 | Data display method and device |
| CN113379487A (en) * | 2021-06-01 | 2021-09-10 | 北京京东拓先科技有限公司 | Data sharing method, device and storage medium |
| CN113961161A (en) * | 2021-10-18 | 2022-01-21 | 阿里云计算有限公司 | Data display method, system, mobile terminal, storage medium and program product |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108153877A (en) * | 2017-12-26 | 2018-06-12 | 平安科技（深圳）有限公司 | Data dictionary methods of exhibiting, device, terminal device and storage medium |
| CN109189383A (en) * | 2018-08-28 | 2019-01-11 | 厦门海迈科技股份有限公司 | The generation method of code file, calculates equipment and storage medium at device |
| CN110187877A (en) * | 2019-05-29 | 2019-08-30 | 浙江大搜车软件技术有限公司 | Icon acquisition methods and device, system, electronic equipment, storage medium |
| CN110309174A (en) * | 2018-03-02 | 2019-10-08 | 阿里巴巴集团控股有限公司 | A kind of data query method, apparatus and server |
| CN110334144A (en) * | 2019-06-13 | 2019-10-15 | 平安银行股份有限公司 | Message methods of exhibiting, device, computer equipment and storage medium |
-
2019
- 2019-10-30 CN CN201911047389.4A patent/CN110888931B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108153877A (en) * | 2017-12-26 | 2018-06-12 | 平安科技（深圳）有限公司 | Data dictionary methods of exhibiting, device, terminal device and storage medium |
| CN110309174A (en) * | 2018-03-02 | 2019-10-08 | 阿里巴巴集团控股有限公司 | A kind of data query method, apparatus and server |
| CN109189383A (en) * | 2018-08-28 | 2019-01-11 | 厦门海迈科技股份有限公司 | The generation method of code file, calculates equipment and storage medium at device |
| CN110187877A (en) * | 2019-05-29 | 2019-08-30 | 浙江大搜车软件技术有限公司 | Icon acquisition methods and device, system, electronic equipment, storage medium |
| CN110334144A (en) * | 2019-06-13 | 2019-10-15 | 平安银行股份有限公司 | Message methods of exhibiting, device, computer equipment and storage medium |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112269613A (en) * | 2020-10-23 | 2021-01-26 | 北京金和网络股份有限公司 | Data display method and device |
| CN113379487A (en) * | 2021-06-01 | 2021-09-10 | 北京京东拓先科技有限公司 | Data sharing method, device and storage medium |
| CN113961161A (en) * | 2021-10-18 | 2022-01-21 | 阿里云计算有限公司 | Data display method, system, mobile terminal, storage medium and program product |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110888931B (en) | 2022-05-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110888931B (en) | Data display method and device, server, terminal equipment and readable storage medium | |
| US9558218B2 (en) | Truncating data associated with objects in a multi-tenant database | |
| US9015118B2 (en) | Determining and presenting provenance and lineage for content in a content management system | |
| JP2021518021A (en) | Data processing methods, equipment and computer readable storage media | |
| JP5555809B2 (en) | System and method for television search assistant | |
| US20140067548A1 (en) | Saving on device functionality for business calendar | |
| CN110750969A (en) | Method and device for generating report | |
| JP2019087249A5 (en) | ||
| US20200089687A1 (en) | Collaborative search of databases | |
| US20230066096A1 (en) | Data transfer in a computer-implemented database | |
| CN111984657B (en) | Data collection method, device, storage medium and computer equipment | |
| US7809741B2 (en) | Generating and utilizing composite keys in lieu of compound keys | |
| CN111190895A (en) | Method and device for organizing columnar storage data and storage medium | |
| US10911592B2 (en) | Method and system for defining an offlinable model graph | |
| US9087127B1 (en) | Method for providing an integrated video module | |
| US11995584B2 (en) | Training assignment tool | |
| CN105260425A (en) | Cloud disk based file display method and apparatus | |
| US20220358445A1 (en) | Training assignment tool | |
| US10229128B2 (en) | Method and apparatus for the generation, organization, storage and retrieval of time stamped blocks of data | |
| WO2019118748A1 (en) | Spatial and temporal data storage and retrieval | |
| US20210232371A1 (en) | Composition enablement for partner and customer extensibility of inversion of control objects | |
| CN117853065A (en) | Data management method, device and medium for ERP system | |
| CN117632544A (en) | Task processing method, device and equipment based on stock data call | |
| CN114781333A (en) | Method and device for converting information of agent | |
| CN114077606A (en) | Data processing method and device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |