Method and system for managing database

• US 8,626,779 B2
• Filed: 10/28/2008
• Issued: 01/07/2014
• Est. Priority Date: 12/21/2007
• Status: Active Grant

• Current Assignee: Naver Corporation
• Original Assignee: NHN Business Platform Corp. (Naver Corporation)
• Inventors: Lee, Hye Jung, Park, Kieun, Kim, Gabyoung, Lee, Jong Min
• Primary Examiner(s): MORRISON, JAY A
• Application Number:
  US12/259,956
• Publication Number:
  US 20090164415A1
• Time in Patent Office: 1,897 Days
• Field of Search: None
• US Class Current: 707/758
• CPC Class Codes: G06F 16/2308 Concurrency control transaction processing G06F9/466
• CPC Class Codes: G06F 16/24534 Query rewriting; Transformation

Abstract

A method and system for managing database is disclosed, which is capable of simultaneously performing a data selection procedure and a data click-count update procedure when specific data is selected, the method comprising receiving and analyzing a query in which both a fetch request for a record included in a specific database table and an update request for at least one of columns included in the record are defined together; generating an execution plan to execute the analyzed query; and executing the execution plan by fetching the record and updating at least one of the columns according to the execution plan.

Claims

1. A computer-implemented database-managing method comprising:

receiving and analyzing, by the computer, a single statement that comprises a fetch request for a record in a database table and an update request for updating at least one column;

generating an execution plan to execute the single statement, the execution plan including a locking time for preventing access to the record while the single statement is processed, the locking time ending once the single statement is processed and before the update request is made permanent;

matching an entry comprised of a record ID and a column ID with a column value corresponding to the column ID included in the entry, and storing the entry and column value matched with each other in a memory;

executing the execution plan by fetching the record in accordance with the fetch request and updating the at least one column in accordance with the update request, the executing including,

updating the column value matched with the entry according to the update request,

reflecting the column value kept in the memory on the database table in response to a specific condition being satisfied, and

updating a click count of content in the corresponding column; and

presenting the record in accordance with the fetch request.

2. The computer-implemented database-managing method of claim 1, wherein the analyzing the statement comprises:

receiving the statement;

parsing the received statement; and

checking validation for the parsed statement.

3. The computer-implemented database-managing method of claim 2, wherein the analyzing the statement further comprises generating a parse tree for the statement through the use of parsing results after parsing the statement, the validation of the generated parse tree is checked in the checking the validation for the parsed statement, and the execution plan for the valid parse tree is generated in the generating the execution plan.

4. The computer-implemented database-managing method of claim 1, wherein the record comprises content in a specific bulletin board.

5. The computer-implemented database-managing method of claim 1, wherein the executing the execution plan comprises:

generating a transaction to execute the execution plan;

fetching the record from the database table;

obtaining a value recorded in at least one of the columns requested for the update among the fetched record;

updating the obtained value recorded in the column; and

completing the transaction by noticing completion of the update.

6. The computer-implemented database-managing method of claim 5, wherein the executing the execution plan further comprises:

generating and executing a sub-transaction to update the information recorded in the column.

7. The computer-implemented database-managing method of claim 6, wherein locks for the database table and record are set during a period of processing the sub-transaction for the update of the column.

8. The computer-implemented database-managing method of claim 5, wherein the fetching the record is performed by a sequential-scanning method, an index-scanning method, or both the sequential-scanning method and the index-scanning method.

9. The computer-implemented database-managing method of claim 1, wherein an index for the column and the value recorded in the column are updated in response to a determination that the index for the column exists in the execution plan.

10. The computer-implemented database-managing method of claim 1, wherein the column value is reflected on the database table in response to a determination that the column value kept in the memory is greater than a first reference value, or a determination that the column value is maintained for a time period longer than a second reference value from a finally-updated time point in the reflecting the column value.

11. The computer-implemented database-managing method of claim 1, wherein the entry and column value are stored through the use of a hash table.

12. The computer-implemented database-managing method of claim 1, wherein updating the column value comprises determining whether the entry for the column exists, and updating the column value matched with the entry in response to a determination that the entry for the column exists.

13. The computer-implemented database-managing method of claim 12, further comprising:

adding the entry for the column in response to a determination that there is no entry for the column; and

storing the column value of the column in the memory, the column value being matched with the added entry.

14. The computer-implemented database-managing method of claim 13, wherein the adding the entry comprises:

determining whether the entry can be added to the memory; and

adding the entry to the memory in response to a determination that the entry can be added to the memory.

15. One or more computer-readable media having stored thereon a computer program that, when executed by one or more processors, causes the one or more processors to perform acts comprising:

receiving and analyzing a single statement that comprises a fetch request for a record in a database table and an update request for updating at least one column;

generating an execution plan to execute the analyzed statement, the execution plan including a locking time for preventing access to the record while the single statement is processed, the locking time ending once the single statement is processed and before the update request is made permanent;

matching an entry comprised of a record ID and a column ID with a column value corresponding to the column ID included in the entry, and storing the entry and column value matched with each other in a memory;

executing the execution plan by fetching the record in accordance with the fetch request and updating the at least one column according to the update request, wherein executing the execution plan includes,

generating a transaction for updating after fetching the record;

updating a click count of content in the corresponding column;

updating the value recorded in the column;

updating the column value matched with the entry according to the update request,

reflecting the column value kept in the memory on the database table in response to a specific condition being satisfied; and

completing the transaction after updating, wherein a lock for the database table and record is set during the transaction for updating; and

presenting the record in accordance with the fetch request.

16. A database-managing system comprising:

a processor; and

a memory including instructions, which when executed by the processor, cause the processor to implement;

a query analyzer configured to receive and analyze a single statement that comprises a fetch request for a record in a database table and an update request for updating at least one column;

an execution plan generator configured to generate an execution plan to execute the analyzed statement, the generated execution plan including a locking time for preventing access to the record while the single statement is processed, the locking time ending once the single statement is processed and before the update request is made permanent;

an entry manager configured to match an entry comprised of a record ID and a column ID with the column value corresponding to the column ID included in the entry, and configured to store the entry and column value matched with each other in a memory;

an execution plan executor configured to execute the execution plan by fetching the record in accordance with the fetch request and updating the at least one column according to the update request, and during the updating the execution plan executor is configured to

update the column value matched with the entry for the column in the memory,

reflect the column value kept in the memory on the database table in response to a determination that a specific condition is satisfied, and

update a click count of content in the corresponding column; and

a presenter configured to present the record in accordance with the fetch request.

17. The database-managing system of claim 16, wherein the query analyzer comprises:

a query receiver configured to receive the statement;

a parser configured to parse the statement received by the query receiver; and

a validation checker configured to check whether or not the parsed statement is valid,

wherein the execution plan generator is configured to generate the execution plan for the statement determined as valid by the validation checker.

18. The database-managing system of claim 17, wherein the parser is configured to generate a parse tree for the statement through the use of parsing results, the validation checker is configured to check validation for the parse tree generated by the parser, and the execution plan generator is configured to generate an execution plan for the valid parse tree among the parse trees.

19. The database-managing system of claim 16, wherein the execution plan executor is configured to generate a transaction to execute the execution plan, configured to fetch the record from the database table in the transaction, configured to obtain a value recorded in the column among the fetched records, and configured to update the obtained value recorded in the column.

20. The database-managing system of claim 19, wherein the execution plan executor is configured to generate a sub-transaction for the update of the value recorded in the column during a period of processing the transaction, and is configured to perform the update of the value recorded in the column in the sub-transaction.

21. The database-managing system of claim 20, wherein the execution plan executor is configured to set a lock for the database table and record during a period of processing the sub-transaction.

22. The database-managing system of claim 16, wherein the execution plan executor is configured to reflect the column value on the database table in response to a determination that the column value kept in the memory is larger than a first reference value, or a determination that the column value is maintained for a time period longer than a second reference value from a finally-updated time point.

23. The database-managing system of claim 16, wherein the entry manager is configured to store the entry and column value in the memory through the use of a hash table.

24. The database-managing system of claim 16, wherein the execution plan executor is configured to determine whether the entry for the column exists, and configured to provide the entry-addition request for the column to the entry manager in response to a determination that there is no entry for the column;

and the entry manager is configured to add the entry for the column corresponding to the entry-addition request.

25. The database-managing system of claim 24, wherein the entry manager is configured to determine whether the entry can be added to the entry in response to receiving the entry-addition request from the execution plan executor;

configured to delete any one of the entries stored in the memory in response to a determination that the entry cannot be added to the memory; and

configured to add the entry for the column to the memory.