WO2000043916A9 - Database item versioning - Google Patents
Database item versioningInfo
- Publication number
- WO2000043916A9 WO2000043916A9 PCT/US2000/001472 US0001472W WO0043916A9 WO 2000043916 A9 WO2000043916 A9 WO 2000043916A9 US 0001472 W US0001472 W US 0001472W WO 0043916 A9 WO0043916 A9 WO 0043916A9
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- database
- stream
- item
- computer
- scc
- Prior art date
Links
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/24—Querying
- G06F16/242—Query formulation
- G06F16/2433—Query languages
- G06F16/2443—Stored procedures
-
- 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/21—Design, administration or maintenance of databases
- G06F16/219—Managing data history or versioning
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99944—Object-oriented database structure
- Y10S707/99945—Object-oriented database structure processing
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99951—File or database maintenance
- Y10S707/99952—Coherency, e.g. same view to multiple users
- Y10S707/99954—Version management
Definitions
- This invention relates generally to databases such as Structured Query Language (SQL) databases, and more particularly to the versioning of items such as text-stream stored procedures (SP's) of such databases.
- SQL Structured Query Language
- SQL Structured Query Language
- SQL commands can be used to interactively work with a database or can be embedded within a programming language to interface to a database.
- Programming extensions to SQL have turned it into a full-blown database programming language.
- a stored procedure is a SQL program that is stored in the database, and which is executed by calling it directly from a client or from a database trigger.
- the SQL procedure is stored in the database, for example, it does not have to be replicated in each client. This saves programming effort, especially when different client user interfaces and development systems are used.
- a stored procedure can be viewed as a standard computer program in some respects, with one important difference: while standard computer programs are usually stored as one or more files on a storage such as a hard disk drive, a stored procedure is not stored as a separate file or files, but rather as text and binary streams within the database itself.
- a system includes a program such as an editor, a database, a source code control (SCC) system, and a mechanism.
- An editor program provides for the editing of an item such as a stored procedure of a database such as a SQL database.
- the database includes the stored procedure (for example, a version of the stored procedure), and the source code control system stores versions of the stored procedure.
- the mechanism provides for the checking in and checking out of the stored procedures.
- the invention is applicable to any other item of databases, including but not limited to: views, triggers, constraints, persisted queries and scripts for creating any database object, such as tables, indexes, domains, etc., as those of ordinary skill within the art can appreciate.
- the mechanism that provides for checking in and checking out of the stored procedures of the database provides for effective versioning of the stored procedures.
- the mechanism keeps track of users who wish to edit the stored procedures, and once they have been changed, the mechanism keeps track of the changes that have been made to the stored procedures.
- FIG. 1 shows a computer in conjunction with which embodiments of the invention may be practiced
- FIG. 2 shows a diagram of a computerized system in accordance with an embodiment of the invention
- FIG. 3 shows a flowchart of a check-out method according to an embodiment of the invention.
- FIG. 4 shows a flowchart of a check-in method according to an embodiment of the invention.
- ontrole par Scanne par. include, but are not limited to, views, triggers, constraints, persisted queries and scripts for creating any database object, such as tables, indexes, domains, etc.
- FIG. 1 a diagram of the hardware and operating environment in conjunction with which embodiments of the invention may be practiced is shown.
- the description of FIG. 1 is intended to provide a brief, general description of suitable computer hardware and a suitable computing environment in conjunction with which the invention may be implemented.
- the invention is described in the general context of computer-executable instructions, such as program modules, being executed by a computer, such as a personal computer.
- program modules include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types.
- the invention may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PC's, minicomputers, mainframe computers, and the like.
- the invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network.
- program modules may be located in both local and remote memory storage devices.
- the exemplary hardware and operating environment of FIG. 1 for implementing the invention includes a general purpose computing device in the form of a computer 20, including a processing unit 21, a system memory 22, and a system bus 23 that operatively couples various system components include the system memory to the processing unit 21.
- a general purpose computing device in the form of a computer 20, including a processing unit 21, a system memory 22, and a system bus 23 that operatively couples various system components include the system memory to the processing unit 21.
- the computer 20 may be a conventional computer, a distributed computer, or any other type of computer; the invention is not so limited.
- the system bus 23 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures.
- the system memory may also be referred to as simply the memory, and includes read only memory (ROM) 24 and random access memory (RAM) 25.
- ROM read only memory
- RAM random access memory
- the computer 20 further includes a hard disk drive 27 for reading from and writing to a hard disk, not shown, a magnetic disk drive 28 for reading from or writing to a removable magnetic disk 29, and an optical disk drive 30 for reading from or writing to a removable optical disk 31 such as a CD ROM or other optical media.
- the hard disk drive 27, magnetic disk drive 28, and optical disk drive 30 are connected to the system bus 23 by a hard disk drive interface 32, a magnetic disk drive interface 33, and an optical disk drive interface 34, respectively.
- the drives and their associated computer-readable media provide nonvolatile storage of computer-readable instructions, data structures, program modules and other data for the computer 20. It should be appreciated by those skilled in the art that any type of computer-readable media which can store data that is accessible by a computer, such as magnetic cassettes, flash memory cards, digital video disks, Bernoulli cartridges, random access memories (RAMs), read only memories (ROMs), and the like, may be used in the exemplary operating environment.
- a number of program modules may be stored on the hard disk, magnetic disk 29, optical disk 31 , ROM 24, or RAM 25, including an operating system 35, one or more application programs 36, other program modules 37, and program data 38.
- a user may enter commands and information into the personal computer 20 through input devices such as a keyboard 40 and pointing device 42.
- Other input devices may include a microphone, joystick, game pad, satellite dish, scanner, or the like.
- These and other input devices are often connected to the processing unit 21 through a serial port interface 46 that is coupled to the system bus, but may be connected by other interfaces, such as a parallel port, game port, or a universal serial bus (USB).
- a monitor 47 or other type of display device is also connected to the system bus 23 via an interface, such as a video adapter 48.
- computers typically include other peripheral output devices (not shown), such as speakers and printers.
- the computer 20 may operate in a networked environment using logical connections to one or more remote computers, such as remote computer 49.
- the remote computer 49 may be another computer, a server, a router, a network PC, a client, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 20, although only a memory storage device 50 has been illustrated in FIG. 1.
- the logical connections depicted in FIG. 1 include a local- area network (LAN) 51 and a wide-area network (WAN) 52.
- LAN local- area network
- WAN wide-area network
- the computer 20 When used in a LAN-networking environment, the computer 20 is connected to the local network 51 through a network interface or adapter 53, which is one type of communications device.
- the computer 20 When used in a WAN-networking environment, the computer 20 typically includes a modem 54, a type of communications device, or any other type of communications device for establishing communications over the wide area network 52, such as the Internal.
- the modem 54 which may be internal or external, is connected to the system bus 23 via the serial port interface 46.
- program modules depicted relative to the personal computer 20, or portions thereof may be stored in the remote memory storage device. It is appreciated that the network connections shown are exemplary and other means of and communications devices for establishing a communications link between the computers may be used.
- the computer in conjunction with which embodiments of the invention may be practiced may be a conventional computer, a distributed computer, or any other type of computer; the invention is not so limited.
- a computer typically includes one or more processing units as its processor, and a computer-readable medium such as a memory.
- the computer may also include a communications device such as a network adapter or a modem, so that it is able to communicatively couple other computers.
- the system includes a database 200, a SCC system 202, a mechanism 204, and an editor 206.
- the system may be implemented over one or more computers, such as that described in the preceding section of the detailed description. In the case where the system is implemented over more than one computer, it may be implemented in what is known as a client-server architecture, or in what is known as a distributed system. The invention is not limited to a particular architecture, however, for the implementation of the system of FIG. 2.
- the database 200 may be any type of database, such as a SQL database known in the art.
- the database 200 stores records, or data, and also code, such as stored procedures as have been described in the background section.
- stored procedure 208 is a binary stream including a compiled part 210 and a text part 212 (those of ordinary skill within the art can appreciate that the part 210 and the part 212 can in another embodiment be stored as separated streams).
- the text part 212 acts as the source code of the compiled part 210. Those of ordinary skill within the art can appreciate, however, that the text part 212 may not be present, such that only the compiled part 210 is present.
- the SCC system 202 stores versions of stored procedures, such as the stored procedure 208 stored in the database 200, and the stored procedure 214.
- the stored procedure 214 also has a compiled part 216 and a text part 218.
- the text part 218 of the stored procedure 214 acts as the source code of the compiled part 216.
- the text part 218 may not be present, such that only the compiled part 216 is present.
- the SCC system 202 is Visual Source Safe, from Microsoft Corp., which is a stand-alone product shipped as part of Visual Studio, a development environment for developing code such as stored procedures available from Microsoft Corp.
- the Visual Source Safe has OLE automation interfaces, as known in the art, for checking in and checking out different versions of code, such as stored procedures.
- the invention is not limited, however, to the embodiment utilizes Visual Source Safe and/or Visual Studio.
- the SCC system 202 is not limited to only handling database (e.g., SQL database) streams, but in other embodiments of the invention, can store other types of streams, such as including but not limited to: C code, Microsoft Word or other word processor documents, etc.
- database e.g., SQL database
- other types of streams such as including but not limited to: C code, Microsoft Word or other word processor documents, etc.
- checking out refers to the concept of tagging a given item such as a stored procedure such that the item is "in use” by a given user and otherwise cannot be edited or modified by another user (although this second user may be able to use a read-only version of the stored procedure), until the item has been checked back in.
- checking in refers to the concept of tagging a given item that has been previously checked out by a given user such that this user is finished modifying or editing the item ⁇ such that other users are now able to check out the item for their own modification, editing, etc.
- the SCC system 202 is able to store different versions of the same piece of code - such as different versions of the same stored procedure.
- a stored procedure is checked out, for example, edited, saved to the database, and checked back in, the new version of the stored procedure is saved to the SCC system, in a manner that provides for the changes between the new version and the previous version or versions to be viewed. That is, a change or version history of a given stored procedure can be provided by the SCC system 202.
- the mechanism 204 is the manner by which a given stored procedure is actually checked into and out of the SCC system, so that the stored procedure of a database is not modified without versioning of the stored procedure taking place. Versioning is the process by which different versions of the stored procedure are kept track of, for example, by the SCC system 202. Thus, as shown in FIG. 2, a stored procedure of the database 200 cannot be accessed without the mechanism 204 knowing about the access, such that if modifications are made thereto, the mechanism 204 is able to indicate such changes as a new version of the stored procedure via the SCC system 202.
- the database system 200 is itself able to invoke the mechanism 204, on any read access to the stream 212, to provide the benefits of the invention to users who do not choose to use the editor 206 as the computer program used to manipulate the stream 212, as described in the next paragraph.
- the editor 206 is a specific type of a computer program that manipulates the stored procedures of the database 200.
- the editor 206 is a program that provides for the editing of the stored procedures of the database 200.
- the invention is not so limited to a program that is an editor program, however — that is, the invention is amenable to any type of computer program that is used to manipulate database items such as stored procedures of the database 200.
- the editor 206 is part of the Visual Studio development environment already described, such that the editor 206 includes a "data view" of all the tables and the stored procedures, among other data and code, stored in the database 200.
- the invention is not so limited, however.
- the system of FIG. 2 operates as follows.
- the editor 206 desires to retrieve a stored procedure of the database 200 for editing and modification.
- the editor 206 requests to check out the stored procedure, such that the mechanism 204 checks out the desired stored procedure thereto.
- the mechanism 204 does this as follows. It retrieves the stored procedure as stored in the database 200, as well as the same stored procedure as stored in the SCC system 202.
- the version of the stored procedure in the database 200 is the same as in the SCC system 202, then this version is provided to the editor 206. Otherwise, the editor 206 has the ability to choose from either version as the version it wishes to edit and modify. If it is the SCC system version, then this version is automatically saved to the database 200 as the database version, too, by the mechanism 204. Thus, the version of the stored procedure at the database 200 can be either identical to or different than the version of the stored procedure at the SCC system 202.
- the editor 206 Once the editor 206 has edited and modified the stored procedure, it is saved to the database 200 as the database version of the stored procedure. This version is then retrieved by the mechanism 204 to check into the SCC system 202 as the newest version of the stored procedure as saved by the SCC system 202. In other words, the mechanism 204 checks in (i.e., saves) the stored procedure into the SCC system 200, checking in the stored procedure as has been saved to the database 200.
- a check-out method and a check-in method are described. These methods can be performed, for example, by the mechanism 204 of the system of FIG. 2 that has been described in the preceding section, although the invention is not so limited.
- These computer-implemented methods are desirably realized at least in part as one or more programs running on a computer — that is, as a program executed from a computer-readable medium such as a memory by a processor of a computer.
- the programs are desirably storable on a machine-readable medium such as a floppy disk or a CD-ROM, for distribution and installation and execution on another computer.
- the check-out method of FIG. 3 is a manner by which a stored procedure can be checked out from a SCC system, according to one embodiment. It may be performed, for example, when an editor or other program indicates to the mechanism that it wishes to edit or otherwise manipulate the stored procedure.
- the desired stored procedure is checked out from the SCC system - that is, it is indicated to the SCC system that the stored procedure is to be indicated as checked out.
- the SCC system version of the stored procedure stream is retrieved, and in 304, the database version of the stored procedure stream is retrieved.
- the SCC system version of the stored procedure stream is compared to the database version of the stored procedure stream. If they are the same, then the method is done at 308 - that is, the editor or other program can now conduct editing or other manipulation of the stored procedure. Otherwise, in 310, the user is asked to select either the SCC system version or the database version of the stored procedure stream. For example, this may be accomplished within the editor or other program that will be used to edit or otherwise manipulate the desired source procedure. If the database version is chosen, then the method proceeds from 312 to 308, and is done - that is, the editor or other program can now conduct editing or other manipulation of the stored procedure.
- the mechanism saves the SCC system version of the stored procedure stream to the database (such that the database version of the stored procedure stream is now the same as the SCC system version), and the method also ends at 308, where the editor or other program can now conduct editing or other manipulation of the stored procedure.
- the procedure must be checked back into the SCC system. This is accomplished by the method shown in FIG. 4.
- the method of FIG. 4 assumes that the stored procedure stream has already been saved by the editor or other program back to the database; however, the invention is not so limited - for example, this functionality can also be performed within the context of the method of FIG. 4, too.
- the stored procedure stream is retrieved by the mechanism, from the database (if the stream as modified or edited has not already been saved to the database, then this is first accomplished).
- this version of the stored procedure stream is checked back into the SCC system. That is, the stored procedure stream is saved to the SCC system as the newest version of this stored procedure. Furthermore, the SCC system is also told to indicate that the stored procedure stream has now been checked in, such that it may be subsequently check out. In at least one embodiment of the invention, for example, a stored procedure stream cannot be checked out unless it is indicated in the SCC system as having been checked in - that is, two different programs cannot check out the same stored procedure stream at the same time. The invention is not so limited, however.
- the method of FIG. 4 ends at 404.
Abstract
Description
Claims
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU34721/00A AU3472100A (en) | 1999-01-21 | 2000-01-12 | Database item versioning |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/235,038 | 1999-01-21 | ||
US09/235,038 US7296037B1 (en) | 1999-01-21 | 1999-01-21 | Database item versioning |
Publications (3)
Publication Number | Publication Date |
---|---|
WO2000043916A2 WO2000043916A2 (en) | 2000-07-27 |
WO2000043916A3 WO2000043916A3 (en) | 2001-02-15 |
WO2000043916A9 true WO2000043916A9 (en) | 2002-05-02 |
Family
ID=22883828
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2000/001472 WO2000043916A2 (en) | 1999-01-21 | 2000-01-21 | Database item versioning |
Country Status (3)
Country | Link |
---|---|
US (2) | US7296037B1 (en) |
AU (1) | AU3472100A (en) |
WO (1) | WO2000043916A2 (en) |
Families Citing this family (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6931630B1 (en) | 2000-09-27 | 2005-08-16 | International Business Machines Corporation | Method of, system for, and computer program product for providing automatic identification of a computer program code candidate for web deployment or a stored procedure |
US7110936B2 (en) * | 2001-02-23 | 2006-09-19 | Complementsoft Llc | System and method for generating and maintaining software code |
JP2008533544A (en) * | 2004-09-20 | 2008-08-21 | コダーズ,インコーポレイテッド | Method and system for operating a source code search engine |
US20070299825A1 (en) * | 2004-09-20 | 2007-12-27 | Koders, Inc. | Source Code Search Engine |
US20070168975A1 (en) * | 2005-12-13 | 2007-07-19 | Thomas Kessler | Debugger and test tool |
US7818660B2 (en) | 2006-01-29 | 2010-10-19 | Litera Technology Llc | Method of compound document comparison |
US8166003B2 (en) * | 2006-05-05 | 2012-04-24 | Microsoft Corporation | Permission-based document server |
US7979450B2 (en) * | 2008-09-15 | 2011-07-12 | Xsevo Systems, Inc. | Instance management of code in a database |
US8566294B2 (en) | 2008-12-29 | 2013-10-22 | International Business Machines Corporation | Database element versioning system and method |
US10685177B2 (en) * | 2009-01-07 | 2020-06-16 | Litera Corporation | System and method for comparing digital data in spreadsheets or database tables |
US8136031B2 (en) | 2009-03-17 | 2012-03-13 | Litera Technologies, LLC | Comparing the content of tables containing merged or split cells |
US8386429B2 (en) * | 2009-03-31 | 2013-02-26 | Microsoft Corporation | Generic editor for databases |
US8983983B2 (en) | 2010-02-04 | 2015-03-17 | Network State, LLC | State operating system |
US9436727B1 (en) * | 2013-04-01 | 2016-09-06 | Ca, Inc. | Method for providing an integrated macro module |
US11080462B2 (en) | 2017-11-13 | 2021-08-03 | Workshare Ltd. | Method of comparing two data tables and displaying the results without source formatting |
US11263193B2 (en) * | 2018-11-19 | 2022-03-01 | Clover Health | Generating tables using data records |
US11294664B2 (en) * | 2020-06-05 | 2022-04-05 | CrossVista, Inc. | Version control system |
US11354118B2 (en) * | 2020-06-05 | 2022-06-07 | Cross Vista, Inc. | Version control system |
Family Cites Families (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4558413A (en) * | 1983-11-21 | 1985-12-10 | Xerox Corporation | Software version management system |
US4809170A (en) * | 1987-04-22 | 1989-02-28 | Apollo Computer, Inc. | Computer device for aiding in the development of software system |
CA2025160A1 (en) * | 1989-09-28 | 1991-03-29 | John W. White | Portable and dynamic distributed applications architecture |
US5894314A (en) * | 1991-01-18 | 1999-04-13 | Canon Kabushiki Kaisha | Ink jet recording apparatus using thermal energy |
US5386559A (en) * | 1992-07-16 | 1995-01-31 | International Business Machines Corporation | Variant domains and variant maps in a versioned database management system |
US5652884A (en) * | 1994-11-14 | 1997-07-29 | Object Technology Licensing Corp. | Method and apparatus for dynamic update of an existing object in an object editor |
US5724556A (en) * | 1995-04-14 | 1998-03-03 | Oracle Corporation | Method and apparatus for defining and configuring modules of data objects and programs in a distributed computer system |
US5805889A (en) * | 1995-10-20 | 1998-09-08 | Sun Microsystems, Inc. | System and method for integrating editing and versioning in data repositories |
US6349407B1 (en) * | 1995-12-29 | 2002-02-19 | Sun Microsystems, Incorporated | Method and apparatus for re-introducing version control |
US6112024A (en) * | 1996-10-02 | 2000-08-29 | Sybase, Inc. | Development system providing methods for managing different versions of objects with a meta model |
US5950209A (en) * | 1996-10-02 | 1999-09-07 | Alcatel Usa Sourcing, L.P. | Software release control system and method |
US6145119A (en) * | 1997-03-31 | 2000-11-07 | International Business Machines Corporation | Programming development environment for intranet and internet applications employing unique project data structure |
US6094684A (en) * | 1997-04-02 | 2000-07-25 | Alpha Microsystems, Inc. | Method and apparatus for data communication |
US6226652B1 (en) * | 1997-09-05 | 2001-05-01 | International Business Machines Corp. | Method and system for automatically detecting collision and selecting updated versions of a set of files |
US5966707A (en) * | 1997-12-02 | 1999-10-12 | International Business Machines Corporation | Method for managing a plurality of data processes residing in heterogeneous data repositories |
US6260040B1 (en) * | 1998-01-05 | 2001-07-10 | International Business Machines Corporation | Shared file system for digital content |
US6279151B1 (en) * | 1998-01-20 | 2001-08-21 | International Business Machines Corporation | Method and apparatus for remote source code inclusion |
US6393437B1 (en) * | 1998-01-27 | 2002-05-21 | Microsoft Corporation | Web developer isolation techniques |
US6457176B1 (en) * | 1999-06-25 | 2002-09-24 | International Business Machines Corporation | System and method for source code processing |
US6449624B1 (en) * | 1999-10-18 | 2002-09-10 | Fisher-Rosemount Systems, Inc. | Version control and audit trail in a process control system |
-
1999
- 1999-01-21 US US09/235,038 patent/US7296037B1/en not_active Expired - Fee Related
-
2000
- 2000-01-12 AU AU34721/00A patent/AU3472100A/en not_active Abandoned
- 2000-01-21 WO PCT/US2000/001472 patent/WO2000043916A2/en active Application Filing
-
2004
- 2004-06-15 US US10/868,111 patent/US7444363B2/en not_active Expired - Fee Related
Also Published As
Publication number | Publication date |
---|---|
AU3472100A (en) | 2000-08-07 |
WO2000043916A2 (en) | 2000-07-27 |
US20040230616A1 (en) | 2004-11-18 |
US7444363B2 (en) | 2008-10-28 |
WO2000043916A3 (en) | 2001-02-15 |
US7296037B1 (en) | 2007-11-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7296037B1 (en) | Database item versioning | |
US6360225B1 (en) | System, method and computer program product for host variable support | |
US7152224B1 (en) | Versioned project associations | |
Douglas et al. | PostgreSQL: a comprehensive guide to building, programming, and administering PostgresSQL databases | |
US5930793A (en) | Performance optimization in a heterogeneous, distributed database environment | |
US6804663B1 (en) | Methods for optimizing the installation of a software product onto a target computer system | |
US8566810B2 (en) | Using database knowledge to optimize a computer program | |
US6714935B1 (en) | Management of non-persistent data in a persistent database | |
EP1121640A1 (en) | Apparatus and method for building modeling tools | |
US7792851B2 (en) | Mechanism for defining queries in terms of data objects | |
Matthews et al. | MySQL and Java developer's guide | |
US6757690B2 (en) | Method and system for monitoring and securing data access in a database system | |
US7127448B1 (en) | Reforming queries to selectively audit accesses to rows within a relational database | |
Rankins et al. | Microsoft SQL Server 2000 Unleashed | |
US8090943B1 (en) | Preventing unauthorized access of routines in a library | |
US7831633B1 (en) | Methods and apparatus for implementing a custom driver for accessing a data source | |
Heller | Modify data with advanced DML | |
US20050177556A1 (en) | Systems and methods for transforming SQL syntax trees into relational algebra representations | |
Watson | Beginning C# 2005 databases | |
Miszczyk et al. | DB2 UDB for AS/400 Object Relational Support | |
Lockhart | Postgresql tutorial | |
Owens | Programming Oracle Triggers and Stored Procedures | |
Sheedy | Sorceress: a database approach to software configuration management | |
Christensen et al. | A COMPARBON OF SELF-CONTAINED AND EMBEDDED DATABASE LANGUAGES. | |
Hotka | Oracle9i Development by Example |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A2 Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A2 Designated state(s): GH GM KE LS MW SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
AK | Designated states |
Kind code of ref document: A3 Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A3 Designated state(s): GH GM KE LS MW SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
COP | Corrected version of pamphlet |
Free format text: PAGES 1/4-4/4, DRAWINGS, REPLACED BY NEW PAGES 1/3-3/3; DUE TO LATE TRANSMITTAL BY THE RECEIVING OFFICE |
|
122 | Ep: pct application non-entry in european phase |