JP2017534987A - Management method of dividing information objects stored in a single database - Google Patents

Abstract

The present invention relates to an automated management method for dividing information objects stored in a single database into individual pieces. An automated management method for splitting information objects stored in a single database includes creating metadata objects, "shared attributes", setting "shared attributes" parameters, and the current delimiter value. Setting a metadata object named “session parameter” that stores a tenant and / or tenant group ID; identifying a specific tenant and defining a current value for each delimiter metadata object; Assigning each tenant an isolated data area that includes a metadata object with an added “shared attribute” and when writing data to a split information object that includes a “shared attribute” metadata object In the column Comprising the steps of writing a "value, and generating a query for retrieving data from a data area assigned to the tenant. The delimiter refers to the partition information object and provides both complete and partial data partitioning.

Description

The present invention relates to a multi-tenant functional architecture that serves tenants from multiple organizations in an isolated manner, and more specifically, automated management that divides information objects stored in a single database into individual pieces. Relating to the method.
Multi-tenant functionality can be used to serve tenants from various organizations (ie, independent subscribers) in an isolated manner within a single service (equipment or deployment). The key is to ensure that the subscribers remain isolated from each other.

  Known prior art includes a solution US 2013/088632 that describes a method for partitioning table data by adding one or more fields (columns) used as discriminators. .

  However, this method tends to be very time consuming because one or more new discriminator columns must be added to each table or catalog each time.

US Patent Application Publication No. 2013/088632

  The object of the present invention is, for example, without significant modifications to the architecture of the application solution itself, with the application solution in local (“desktop”) mode and multiple subscribers accessing the same web service (“cloud partitioning”). By creating mechanisms and methods for flexible management of data partitioning, i.e. by enabling or disabling data partitioning for the same application solution, to ensure that they can work together in mode is there.

  The technical results of the present invention provide both complete and partial data partitioning. For example, some data can be shared by all organizations (eg bank catalogs), while other data such as business or financial data is tenant specific and only visible to specific organizations And made available.

  Definition

  The configuration is an application solution based on the 1C platform, which is a combination of algorithms, forms and data structures. The main purpose of any configuration is correct record keeping, for example for accounting purposes. The 1C platform is a set of specialized objects used to store subject area specific data, ie constants, catalogs, documents and charts of accounts.

  An attribute is a field in a filled-in catalog or document that is displayed in an application solution. Each attribute is characterized by a property that specifies what type of value it stores and how the user can handle it.

  A delimiter (shared attribute) is a metadata object (configuration object) that enables usage of a single attribute for a number of configuration objects (catalog, document, chart of accounts, constants, etc.). Configuration developers can add and configure “shared attributes” to avoid modifications to standard configuration objects. In other words, developers can set and manage shared attributes for all or some objects, rather than adding a delimiter column to each existing catalog (called “tables” in the prior art). Can do. The “Shared Attributes” object gained certain predefined properties such as name, content (list of objects or catalogs for which shared attributes are to be used), values, usage of split data, etc.

  Metadata is a configuration object that describes the associated data layout and its interaction with the database.

  The session parameter is a shared configuration object. A current value is set and stored in the current 1C: enterprise session. For example, session parameters can be used to restrict access to data at the entry level.

  Technical results are achieved by a combination of the advantages of the invention described below. In a first embodiment of the present invention, a method for automated management of splitting an information object stored in a single database serves as a delimiter and references to at least one split information object and to the delimiter Define at least one metadata object that stores the source of the value, a step of pre-creating a “shared attribute” and how the “shared attribute” is used in one or more split information objects. The step of setting the “shared attribute” parameter, the ID of the tenant and / or tenant group that needs to be allowed access to various partition information objects, and the current delimiter value as well, the “session parameter” Set up a metadata object named Identifying a specific tenant and / or tenant group at the start of a database session, defining current values for each delimiter metadata object, and assigning an isolated data area to each tenant and / or tenant group The region includes a metadata object with an added “shared attribute”, and when writing data to the split information object to which the “shared attribute” metadata object is added, Writing a “shared attribute” value and generating a query to retrieve data from a data area assigned to a particular tenant and / or tenant group.

  For certain embodiments of the present invention, if the “Auto Use” property for the “Shared Attributes” parameter is set to “Used”, then the created “Shared Attributes” will be created with all newly created configuration objects. Similarly, it is automatically added to all existing configuration objects. If the "Auto Use" property for the "Shared Attributes" parameter is set to "Not Used", the attribute is not automatically added to the configuration object, and any object that needs to have a delimiter added is the "Delimiter Content" property Selected.

  In a second embodiment of the present invention, a method for automated management of splitting information objects stored in a single database pre-creates at least two “shared attribute” metadata objects used as delimiters Each object stores a reference to at least one split information metadata object and a source of values for the delimiter, and a conditional split flag that is part of another delimiter itself, Include a reference to a splittable constant containing "true" or "false" in the delimiter that references the split information object, and the ID of the tenant and / or tenant group that needs access to the various split information objects And store the current delimiter value as well. Setting up a metadata object named “meter”, identifying a specific tenant and / or tenant group at the start of a database session and thus defining a value for each delimiter, and each tenant and / or Assigning an isolated database to a tenant group, said database comprising metadata objects for each tenant and / or tenant group using filtering by "shared attribute" value and conditional split flag value Used to allocate the data area, and when writing data to the split information object referenced by the delimiter, writing the delimiter value to the corresponding delimiter column; Nantes and / or data area allocated to the tenant group and generating a query to retrieve the data.

  For certain embodiments of the present invention, the database is accessible by all users, at least for read operations, regardless of the session parameters and conditional partition flag values, in addition to the partition information object, at least one Contains two shared objects. In addition to its content and value, the “shared attribute” object provides an indication of whether the split data can be used in a shared mode that may have at least one of the two values “true” or “false”. Similarly, tenants and / or tenant groups are identified and current session parameters are set when a database session is initiated. When sharing mode is set to true and these users call information objects in the database, the current session parameters are ignored and the split information is ignored, at least for read operations, depending on the program-controlled set of delimiter values. Access is granted to a random set of entries in the object.

DISCLOSURE OF THE INVENTION For example, without significant modifications to the architecture of the application solution itself, the application solution is in local (“desktop”) mode and in a mode in which multiple subscribers access the same web service (“cloud partition”) To ensure that they can work together, the management of data partitioning must be flexible to enable or disable data partitioning for the same application solution. In addition, it can partially isolate data and other data can be shared by all or some tenants while at the same time making that data available to a single participating tenant, etc. You need to enable and disable the partitioning of certain objects in your storage.

  The principle of data partitioning is based on a new configuration object, “Shared Attributes”.

The mode of shared attribute operation is set using the data partition property. There are two modes of this configuration object. That is,
1. When the “Data Split” property is set to “Not Used”, the created configuration object is only used as an attribute included in many (or all) configuration objects.
2. If the “Data Split” property is set to “Split”, the shared attribute is used as a data delimiter.

  This method provides for the management of stored data partitioning and application solution operations within the infobase.

  The first embodiment of the claimed invention represents a relatively simple method of dividing using at least one delimiter.

  In the second embodiment, a more complex method of data partitioning is described using more than one delimiter. The advantage of this method is the ability to manage data partitioning using conditional data partitioning.

  The partitioning mechanism that characterizes the partitioning method provides both partial and complete data partitioning. For example, some data can be shared by all organizations (eg, bank catalogs), while other data, such as business or financial data, is tenant specific and only for a particular organization Displayed and available.

  This approach greatly simplifies the operation and updating of application solutions when a single application solution is used for record keeping in multiple organizations.

  A first embodiment of the splitting method includes creating a single shared attribute metadata object that serves as a delimiter. The delimiter stores a reference to one or more division information objects. The source of the value for the delimiter is indicated as well. Parameters are defined for the delimiter that define how the delimiter is used in one or more split metadata objects. A metadata object named “Session Parameter” is set. It stores IDs for tenants and tenant groups that need access to various partition information objects. It stores the current delimiter value as well. When a database session is initiated, specific tenants and / or tenant groups are identified and current values for each delimiter metadata object are defined. The method similarly includes assigning each tenant and / or tenant group an isolated data area that includes a metadata object with an added “shared attribute”. In addition, when information is written to a split information object in a database that has a shared attribute, the value of the shared attribute is written to the corresponding column. As a result, a query is generated to retrieve data from the data area assigned to a particular tenant and / or tenant group.

  If the created shared attribute needs to be automatically added to all existing configuration objects and all newly created configuration objects, set the Auto Use property in the shared attribute parameter to Use . However, if the “Auto Use” property is set to “Not Used”, the attribute is not automatically added to the configuration object, and objects that need to have delimiters added using the “Content” property of the delimiter. Selected.

  In another embodiment of the splitting method (two or more delimiters), a shared attribute metadata object is similarly created and serves as a delimiter. Unlike the first embodiment, in this embodiment, at least two shared attribute metadata objects are created. The delimiter is assumed to contain a reference to a constant along with the split information object from the database referenced by this delimiter. A constant containing a conditional split flag, “true” or “false”, is part of another delimiter and is split similarly. As in the first embodiment, a metadata object named “session parameter” is set. When a tenant is identified and a session begins, an isolated database containing metadata objects is allocated, and data for each tenant and / or tenant group is filtered by “shared attribute” values and conditional split flag values Used to allocate space. Similar to the first embodiment, this embodiment also includes writing a delimiter value to the corresponding delimiter column and generating a query when writing information to an information object in the database.

  In addition, the database includes a split information object with shared objects that are accessible by all users, at least for read operations, regardless of session parameters and conditional split flag values.

  In addition to its content and value, the “shared attribute” also includes an indication of whether the split data can be used in shared mode. This mode may have at least one of two values: “true” or “false”. When a database session begins, a particular tenant and / or tenant group is identified, i.e. the current session parameters are set.

  In the first embodiment of the present invention, the “data division” property is set to “not used”.

  Consider how this embodiment can be used with 1C software.

  At least one delimiter is created by default in the designer before launching the software. This delimiter is used to automatically split the shared infobase into separate, isolated infobases that are each managed by its own administrator.

  For example, a shared infobase may include multiple infobases, each containing all documents for a particular organization. When an Organization delimiter is used as a standard delimiter in the designer, the shared infobase is divided into a number of infobases, each of which is quarantined, to documents from other quarantined databases. Operates in its own configuration without access.

  Then create a "shared attribute" metadata object. This can be done, for example, by selecting Share-Shared Attributes-Add New Object in the configuration window.

Next, the properties of the shared attribute are specified.
A) The name of the shared attribute is specified by the default property.
B) In the property used,
The content (content property) of the shared attribute is specified using a drop-down menu displayed in the configuration editing window, that is, a list of configuration objects to which the shared attribute is to be added is compiled.

The window used to edit the shared attribute content is divided into two parts, each containing information (use column) about whether the shared attribute should be applied to a particular object. That is,
-The top section lists all the configuration objects that can be included in the shared attribute content,
The lower part lists objects with settings that differ from the default settings defined by the auto-use property of the shared attribute.

  If this property is set to "Use", the bottom of the window lists objects that are not included in the shared attribute content.

  If this property is set to “not used”, the bottom part of the window lists the objects contained in the shared attribute content.

  Configuration objects can be edited at the top or bottom of the window. The edited configuration object will move between parts of the window depending on the value in the used column.

  For each configuration object, the usage column can be set to one of three values.

1. Automatically: The assignment of a configuration object to a shared attribute depends on the value of the shared attribute's automatic use property.
-Use: The configuration object is included in the shared attribute content.
-Not used: The configuration object is not included in the shared attribute content.
2. Usage: The configuration object is included in the shared attribute content regardless of the automatic usage property value.
3. Not used: The configuration object is not included in the shared attribute content regardless of the auto-use property value.

  The following configuration objects: catalogs, documents, characteristic type tables, charts of accounts, calculation type tables, business processes, tasks, information registers, cumulative registers, accounting registers, calculation registers and exchange plans are included in shared attribute content. May be included.

  C) Then use the drop-down menu in the configuration window to select how shared attributes are used in connection with the objects listed in the content properties (auto-use properties).

  If the auto-use property is set to "Use", the created shared attribute will be applied to all existing configuration objects (if use of the shared attribute is enabled for these objects), and to all new Automatically added to the created configuration object.

  If the "Automatic use" property is set to "Not used", the attribute is not automatically added to the configuration object, and objects that need to add a shared attribute are selected using the "Content" property .

  This property is used in the same way when shared attributes are used automatically, but there are objects for which shared attributes should not be added.

  At that time, specify the metadata object named "Session Parameter". It stores the IDs of entities (tenants) and / or entity groups (tenant groups) that need to access various partition information objects.

  Thus, session parameter values are initially set when the system starts. These values store usage instructions and delimiter values based on startup command line options or values specified for the infobase user.

The system then analyzes the entered data, specifically:
The system identifies specific tenants and / or tenant groups, or otherwise sets the current session parameters (eg based on machine ID) and thus defines values for each metadata object;
-The system identifies a specified delimiter value that is used to split the shared infobase (eg, if the delimiter is set to Organization, the system will isolate the shared database by the organization) ),
-The system identifies whether the shared attribute is set, and if so, it determines which configuration objects need to be added.
When all parameters are set, the shared infobase is based on a number of isolated infobases where the shared attributes created are added to the configuration object used by the administrator based on the specified parameters. Divided.

If split shared attributes are conditionally disabled,
1. When reading or writing data, the current value of the session parameter that defines the delimiter value and usage is ignored.
Instead, the following values are used:
Usage attribute-true (default delimiter is used),
Delimiter value-the default value for the delimiter type.
2. When reading or writing infobase users, the current values of session parameters that define delimiter values and usage are ignored.
Instead, the following values are used:
Use attribute-false (no delimiters are used).
Delimiter value-not used.

  In the second embodiment of the present invention, the “data division” property is set to “division”.

1. Prior to startup, at least two delimiters are created in the designer.
-At least one of a number of delimiters is set as a standard (main) delimiter, automatically sharing the shared infobase into a separate, isolated infobase managed by its own administrator Used by default to split.
For example, a shared infobase may include multiple infobases, each containing all documents for a particular organization. When an Organization delimiter is used as a standard delimiter in the designer, the shared infobase is divided into a number of infobases, each of which is quarantined, to documents from other quarantined databases. Operates on its own data area without access.
Another delimiter represents a newly created shared attribute configuration object (sub-delimiter) that can be created, for example, by selecting Shared-Shared Attributes-Add New Object in the configuration window.

  2. Then, as shown above, set shared attribute properties such as its name, usage, and content.

3. Then, using the drop-down menu in the configuration window, select a shared attribute partitioning parameter (data partitioning property) in relation to the object listed in the content property.
In this embodiment, the data partition property is set to partition.
Shared attributes used as delimiters have additional properties that affect the behavior of the system and modify the behavior of configuration objects included in the delimiter content.

  4). Then, using the drop-down menu in the configuration window, select how the delimiter is used in relation to the object included in the delimiter content (partitioned data usage property).

  If the split data usage property is set to “independent”, there is no allowed call to split the object if the current infobase session does not use a delimiter. In this case, the delimiter is likewise not available for object models, query languages, dumps in XML and XDTO formats, and data access restrictions. When split data is written, the system automatically fills the shared attribute value with the value set in the current session.

  This mode can be used when the application solution only uses data from a single data region.

  If the split data usage property is set to “Independent and Shared”, the delimiter can be used or ignored. In this mode, a data area defined by the delimiter value used is available. In this case, delimiters are also available for object models, query languages, dumps in XML and XDTO formats, and data access restrictions.

  If a session does not use part of a delimiter that contains a certain object, handling this object becomes less efficient.

  Use this mode when the application solution primarily deals with data from a single data area (eg while entering a document), while in certain modes it can be used for multiple reports, for example for consolidated reports. Or data from all areas may be used.

  5. Then, using the drop-down menu in the configuration window, select a session parameter (data partition value property) that stores the delimiter value set in the current session. The session parameter type should be an exact match of the delimiter type.

  6). Then, using the drop-down menu in the configuration window, select how the shared delimiter is used (data partition usage property) in relation to the configuration object in the current session.

  The use of shared attribute delimiter management is based on logical or constant types, i.e. if the specified session parameter is set to "true", the (sub) delimiter is used in this session.

  7). Then, using the drop-down menu in the configuration window, select the conditional split parameter.

  Conditional splitting is used when the applied solution is to be used in both split and non-split modes.

  For example, an applied solution can be used offline (in this case the delimiter is included in the solution but not used) or it is unrelated to each other (and has an independent set of data in the infobase) Can be used for.

  Such behavior can be implemented using conditional partitioning, i.e., if the solution is offline, partitioning is disabled and it is enabled in split mode.

The conditional split function is as follows. That is,
-An object storing the delimiter state can be set for a delimiter (or an object included in the delimiter content).
-Changing the value of this object can be for all objects (if conditional split is set for delimiter) or for selected objects (conditional split is included in delimiter content) If set for an object), this delimiter can be used to enable or disable splitting.
-If the delimiter is conditionally disabled, the default value for the delimiter type is used.

  The next step is to specify a metadata object named “Session Parameters”. It stores the IDs of entities (tenants) and / or entity groups (tenant groups) that need to access various partition information objects.

  Thus, session parameter values are initially set when the system starts. These values store the usage instructions and the current value of the delimiter based on the startup command line options or values specified for the infobase user.

The system then analyzes the entered data, specifically:
-It identifies a specific tenant and / or tenant group or otherwise sets the current session parameters (eg based on machine ID) and thus defines a current value for each delimiter metadata object And
-It identifies the specified current delimiter value used to split the shared infobase (eg if the delimiter is set to Organization, the system has isolated the shared database by the organization) Split into databases),
It identifies whether the shared attribute is set and
It identifies the shared attribute usage mode (in this embodiment the shared attribute is used as a delimiter);
It identifies configuration objects that need to be split by shared attributes;
-It identifies the split mode for shared attributes.
When all parameters are set, the shared infobase is divided into a number of isolated databases. Within each isolated database, configuration objects are partitioned (filtered) by shared attributes and joined in a new database based on specified parameters.

[Example 1]
Conditional split using constants set in shared attribute properties.

  Delimiters can be completely disabled using Boolean constants ("true" or "false") that are not separated by attributes.

  The configuration includes a Goods catalog, and a numerical company common attribute is included in the metadata. Conditional splits managed by the Split By Company constant are used for the Company shared attribute.

  If Split By Company = False, it means that the delimiter is not used (split is disabled), and vice versa.

  If splitting is disabled, the availability of the Goods catalog will depend on the split data usage properties.

  When the divided data use property is set to “independent”, any tenant (company) is not permitted to access an entry in the product (Goods) catalog.

  If the property of the shared attribute is set to “Independent and Shared”, all tenants will have access to all entries in the Goods catalog.

[Example 2]
Conditional split set for the object (in the content properties)

  Conditional partitioning can be set for each constituent object included in the delimiter content. In this case, the division is invalidated only for objects for which conditional division is set.

  An embodiment of conditional data partitioning using constants.

  Assume that a developer has written an applicable solution for the primary purpose of customer and inventory accounting. In particular, the application solution includes two data storage entities: a Goods catalog and a Contractors catalog.

  The solution was off-the-shelf for the local “desktop” mode, but it now needs to be adapted to the cloud web service mode. It is expected that at least two subscribers will be granted online access to the solution and each subscriber will maintain accounting records for at least two of its affiliates.

  Assume that there are two subscribers, each holding accounting records for multiple affiliates. An optional list of subscribers and their corresponding affiliates is represented below.

Subscriber A
-Company 1,
-Company 2.
Subscriber B
-Company 3,
-Company 4,
-Company 5.

  Data for all organizations is stored in a single infobase with two catalogs: Contractors and Goods. However, in the most general case, a user of a certain organization must only have access to this particular organization's records.

  Since Organization 1 and Organization 2 are affiliated and managed by the same owner, Subscriber A has Organization 1 and Organization 2 as the entire product (Goods). It is further assumed that one wishes to have access to the catalog. Therefore, Organizations 3, 4 and 5 must be completely isolated in their respective data areas, while later registered and controlled by Organizations 1 and 2 and Subscriber A group. Any other organization that must be able to have shared access to the Goods catalog and be able to see all records related to Subscriber A's goods. At the same time, the data areas of the Contractors catalog remain strictly separated by the organization, regardless of which subscriber they belong to.

  The delimiter contains a number of catalogs, two of which are divided into Contractors and Goods. In the goods catalog, conditional division is further set according to the current value (“true” or “false”) of the split goods constant (“true” or “false”). In this case, the Split Goods constant is divided by the subscriber, ie its value is different for each subscriber. The desired effect is achieved by setting this constant to “true” for subscriber A and “false” for subscriber B.

  The combination of advantages recited in the independent claims of the invention is sufficient for achieving the claimed technical result.

  The authors are convinced that the claimed solution meets all the standards of invention patentability.

The present invention relates to a multi-tenant functional architecture that serves tenants from multiple organizations in an isolated manner, and more specifically, automated management that divides information objects stored in a single database into individual pieces. Relating to the method.
Multi-tenant functionality can be used to serve tenants from various organizations (ie, independent subscribers) in an isolated manner within a single service (equipment or deployment). The key is to ensure that the subscribers remain isolated from each other.

Known prior art includes a solution US 2013/088632 that describes a method for partitioning table data by adding one or more fields (columns) used as discriminators. .
However, this method tends to be very time consuming because each time one or more new discriminator columns must be added to each table or catalog by describing the metadata in a special notation. .

US Patent Application Publication No. 2013/088632

  The object of the present invention is, for example, without significant modifications to the architecture of the application solution itself, with the application solution in local (“desktop”) mode and multiple subscribers accessing the same web service (“cloud partitioning”). By creating mechanisms and methods for flexible management of data partitioning, i.e. by enabling or disabling data partitioning for the same application solution, to ensure that they can work together in mode is there.

  The technical results of the present invention provide both complete and partial data partitioning. For example, some data can be shared by all organizations (eg bank catalogs), while other data such as business or financial data is tenant specific and only visible to specific organizations And made available.

  Definition

  The configuration is an application solution based on the 1C platform, which is a combination of algorithms, forms and data structures. The main purpose of any configuration is correct record keeping, for example for accounting purposes. The 1C platform is a set of specialized objects used to store subject area specific data, ie constants, catalogs, documents and charts of accounts.

  An attribute is a field in a filled-in catalog or document that is displayed in an application solution. Each attribute is characterized by properties that specify what type of value it stores and how the user can handle it.

A delimiter ( common attribute) is a metadata object (configuration object) that enables the use of a single attribute for a number of configuration objects (catalog, document, chart of accounts, constants, etc.). Configuration developers can add and configure “ common attributes” to avoid modifications to standard configuration objects. In other words, developers can set and manage common attributes for all or some objects, rather than adding a delimiter column to each existing catalog (called “tables” in the prior art). Can do. A " common attribute" or «delimiter» object is a certain predefined property such as name, content (list of objects or catalogs for which the common attribute is to be used), value, and others discussed below Got.

The session parameter (access restriction object) is a metadata object ( configuration object) . 1C: A certain current value is set and remains during this session of the enterprise . The use of some parameters of the session allows, for example, to set a set of parameters associated with a particular user that has passed authentication and a session is initiated for that user. Session parameters can be changed programmatically during the session, but this scenario is not widely popular and recommended from the standpoint of ensuring data integrity.

Technical results are achieved by a combination of the advantages of the invention described below. In the first embodiment of the present invention, an automated management method for dividing information objects stored in a single database includes creating at least one object of metadata as a delimiter, and working with a database. Setting / creating an object of restricted access metadata for storage of delimiter values and delimiter usage flags during one session, at least for one shared information object, and Keep the source of the value for the delimiter in the reference delimiter, while at the same time the source is an object of restricted access metadata and the identifier of the user and / or group of users that provide access to the shared information object And working sessions with the database First, identify a specific user, define the associated value for each delimiter in the session and the use of the delimiter, while at the same time the specified value remains in the corresponding object in the access restriction metadata And providing a designated user with an isolated area of data containing the information object to which the delimiter is added, while at the same time delimiter values and delimiter usage flags in the session for each such information object In the data record in the shared information object of the database that the delimiter refers to, define the record available to this user using the filtration performed according to Records the delimiter value held in the object And generating a query for data acquisition from the region of data intended for this user and / or group of users, and at the same time the delimiter has an «automatic use» property, If the property is fixed to the << Use >> value, the created delimiter is added to the database information object, added in the same way to the database created information object, and the << automatic use property is value << not used In the case of ≫, the selection of the information object of the database to which the delimiter is added includes performing “content” according to the property of the delimiter.

In a second embodiment of the present invention, an automated management method for splitting an information object stored in a single database includes creating at least two objects of delimiter metadata and working with the database. Setting / creating a metadata object with restricted access intended for storage of delimiter values during one session, and at least a reference to one shared information object in the database and each delimiter Keep the source of the value for each in the delimiter, and a reference to a constant that is part of another delimiter and that contains a conditional delimiter flag that means "true" or "false" Holding in one of the delimiters for the shared information object of the database referenced by the delimiter, and shared information At the beginning of a session of working with the database and maintaining the identifier of the user and / or group of users that provide access to the object, a specific user is identified and the associated value and delimiter for each delimiter in the session Define a usage flag, and at the same time, the specified value remains in the corresponding object in the access restriction metadata and if the conditional delimiter flag is "true", the delimiter is added Using a filtration that is performed according to the delimiter value and delimiter usage flags in the session at each such information object, while providing an isolated area of data containing the information object to the designated user Define the records available to this user, If the default delimiter flag is set to “true”, then the delimiter refers to the record that is available for this user using a filtration performed by default according to the delimiter value. When recording data in a database shared information object, record the delimiter value stored in the access restriction metadata object in the corresponding column, otherwise record the delimiter value by default in the corresponding column. And generating a query for data acquisition from the region of data intended for this user.

For certain embodiments of the invention, the database is accessible by all tenants , at least for read operations, in addition to the partition information object, regardless of session parameters and conditional partition flag values, Contains two shared objects. The fact that the metadata object, delimiter, together with structure and value indications, includes a property that specifies the possibility of using split data in shared mode, accepting the value, ie "true" or "false", at the same time, A particular user and / or group of users are similarly identified at the beginning of a session of work with the database. When the parameter setting is `` true '' for the shared mode and the delimiter is not used in the current session, it is ignored by the current value of the delimiter in the user's appeal to the database information object, and at least the read operation is performed. In order to provide access to any set of records in the shared information object in response to a program-controlled set of delimiter values.

Disclosure of the invention
For example, it works both in local (“desktop”) mode and in multiple subscriber access mode to web services (“cloud split”) without substantial changes in the architecture of the most applicable decision. There is a requirement to manage the data partitioning, ie to include or switch off the data partitioning for the same applied decision. In addition, separate objects are switched on, particularly in storage associated with tables where some of the data is isolated and only available to certain users and other data will be shared or There is a request to switch off.

  Unlike prototypes, a more flexible way of managing the partitioning of data stored in one information base with the use of two or more delimiters is presented. A feature of the method is that it allows you to apply conditional partitioning and manage the partitioning of data. Such an approach can significantly manage and update the applied decisions when the same applied decisions are used for accounting for several customers in a cloud computing service (further— “subscribers”). make it easier.

  In the basic case, system subscribers and users (ie, those who enter a name and personal password to initiate a session) will match one person, for example, it may be an individual entrepreneur.

  However, when using an accounting system for business of class ERP (Business Resource Management), there are more subscribers-it is holding, some legal entities can be part of holding, It will handle the business direction of this corporation or its holdings.

  In the latter case, each of the subscribers has a narrower isolated area, for example, depending on the user's affiliation criteria to the specific legal or business activity direction (production, trade and tp) entering the holding May need to divide their information space.

  Control is the fact that the parameters of the system, eg representing a standard PC or a server with an established software platform-a DBMS with an object paradigm of data access, are set using specific entity "shared attributes" Thanks to you. In object-oriented programming terminology, it is a class of objects, and each copy of the class is created with a certain name (and remains in the device's memory), and the properties and methods predetermined for this class are Have. At the same time, all object properties “shared attributes” and their interrelationships with other objects provided by the platform make so-called “masters” without having to write program code, request text, access politicians, etc. It can be set using a graphic interface.

  A property of the delimiter metadata object.
  In addition to the standard name and type properties, objects have the following specific properties: That is,
  “Strict split” or shared mode is a logical flag that indicates whether the mode is on or off.
  “Content” is an object reference that refers to one or several information objects that can be divided.
  A “conditional delimiter” is an object reference that refers to an object that includes a flag that indicates whether a conditional delimiter applies to this delimiter.
  The “use delimiter” is an object reference that refers to an access restriction object including a flag for use of the delimiter in the session.
  “Value” is an object reference that refers to an access restriction object including the current value of the delimiter.

  The partitioning mechanism that characterizes the partitioning method allows the data to be partitioned completely or partially. For example, any information, in principle, does not require splitting between several subscribers or organizations, ie it is shared for all organizations (bank or currency official catalog) and some information is , Should be made individually, visible and available only to this particular organization. For example, information about transactions on an organization's bank account.

  Thus, in one information base that stores a set of information objects, (and) information objects, non-divided (general) information objects, information objects that are divided using a delimiter, and (in) two or more There may be information objects that are split using delimiters. Depending on the properties of each object set by the developer of the configuration “shared attribute” in the system, access to the records of each of the three types of objects (both for reading and modification) A certain rule to guarantee is set.

  Suppose that the developer of the configuration provided two delimiters: “Subscriber” and “Organization”. Both delimiters are included conditionally. The system will use certain rules of filtering by default depending on whether the strict partitioning mode (shared mode) is set by the developer.

  According to the method, at least two objects of metadata— “delimiters” —are created. One delimiter is considered to specify a reference to a constant in addition to the information object that can be divided in the database to which this delimiter refers. Constants simultaneously contain conditional separation flags— “true” or “false”, which are part of other delimiters and are themselves split. Similarly, access restriction objects (called "session parameters") are created-they will be used to store the current value of the delimiter. During data recording in the division information object of the database, the value of this delimiter can be written into the corresponding column delimiter, and further filtering can be performed on this value when generating a request.

  In addition, there is an object in the database that has general access in addition to the partition information object, and the object does not depend on the state of the session parameter and the conditional partition flag, at least for the performance of the read operation. Available to all users. At the beginning of the session after user authentication, taking into account all records from the non-split object, and similarly the flag value of the conditional split, the corresponding delimiter value and the corresponding delimiter usage flag, A record from the split information object is provided to the end, selected using filtering that also takes into account whether a strict split mode according to this rule is included or switched off.

  It should be noted that besides the impact on the availability of certain records, the strict partitioning mode affects the assignment of unique identifiers to records as well. If a strict split mode is included, the uniqueness of the record identifier is provided only within each isolated area of the split information object. Thanks to the specified features, for example, determine the overall origin of two datasets that are split at a certain stage, and again eliminate these duplicates in the form of objects with identical identifiers. There is an opportunity to merge the two sets. The split and merge mechanism, however, goes beyond this explanation.

  Conditional partitioning can be set for each object in the configuration that is part of the delimiter. Only the partitioning of objects for which conditional partitioning is configured instead of all objects will be stopped in this case.

An embodiment of conditional data partitioning using example constants.

  Assume that a developer has written an applicable solution for the primary purpose of customer and inventory accounting. In particular, the application solution includes two data storage entities: a Goods catalog and a Contractors catalog.

  The solution was off-the-shelf for the local “desktop” mode, but it now needs to be adapted to the cloud web service mode. It is expected that at least two subscribers will be granted online access to the solution and each subscriber will maintain accounting records for at least two of its affiliates.

  Assume that there are two subscribers, each holding accounting records for multiple affiliates. An optional list of subscribers and their corresponding affiliates is represented below.

Subscriber A
-Company 1,
-Company 2.
Subscriber B
-Company 3,
-Company 4,
-Company 5.

  Data for all organizations is stored in a single infobase with two catalogs: Contractors and Goods. However, in the most general case, a user of a certain organization must only have access to this particular organization's records.

  Since Organization 1 and Organization 2 are affiliated and managed by the same owner, Subscriber A has Organization 1 and Organization 2 as the entire product (Goods). It is further assumed that one wishes to have access to the catalog. Therefore, Organizations 3, 4 and 5 must be completely isolated in their respective data areas, while later registered and controlled by Organizations 1 and 2 and Subscriber A group. Any other organization that must be able to have shared access to the Goods catalog and be able to see all records related to Subscriber A's goods. At the same time, the data areas of the Contractors catalog remain strictly separated by the organization, regardless of which subscriber they belong to.

  Two delimiters are created, each of which refers to both catalogs “Contractors” and “Goods”, and for the second delimiter, the conditional split is the constant Split_Goods in the session. Depending on the available value (“true” or “false”) of In this case, the constant Split_Goods is divided by the subscribers, i.e. has a specific value for each subscriber. And to achieve the required effect, the value must be set to “true” for subscriber A and the value must be set to “false” for subscriber B. .

The feature combinations recited in the independent claims are sufficient for achieving the claimed technical results.

  The authors are convinced that the claimed solution meets all the standards of invention patentability.

Claims (7)

An automated management method for dividing information objects stored in a single database,
Pre-creating at least one “shared attribute” metadata object to be used as a delimiter, wherein the “shared attribute” metadata object is a reference to at least one split information metadata object and a value for the delimiter; Store the source of the steps, and
-Setting parameters for the "shared attributes" that define how the "shared attributes" are used in at least one split metadata object;
-Specify the metadata object named "Session Parameter" that stores the IDs of tenants and / or tenant groups that need access to the various partition information objects and stores the current delimiter value as well Steps,
-Identifying a specific tenant and / or tenant group when a database session begins and defining the current value for each delimiter metadata object;
-Assigning each tenant and / or tenant group an isolated data area containing metadata objects with added "shared attributes";
Writing the “shared attribute” value in the corresponding column when writing data to the split information object to which the “shared attribute” metadata object is added;
Generating a query for retrieving data from the data area assigned to a particular tenant and / or tenant group;
Including a method.   The created “shared attribute” is the same as all newly created configuration objects as well as all newly created configuration objects when the “automatic use” property contained in the “shared attribute” parameter is set to “used”. The method of claim 1, wherein the method is automatically added to an object.   The attribute is not automatically added to the configuration object when the “auto use” property included in the “shared attribute” parameter is set to “not used”, and the delimiter needs to be added. The method of claim 1, wherein an object is selected using the “content” property of the delimiter. An automated management method for dividing information objects stored in a single database,
Pre-creating at least two “shared attribute” metadata objects to be used as delimiters, each object storing a reference to at least one split information metadata object and a source of values for said delimiters; , Steps and
Including in the delimiter referring to the split information object a reference to a splittable constant comprising a conditional split flag, “true” or “false”, which is part of another delimiter itself;
The metadata named “session parameter”, which stores the IDs of tenants and / or tenant groups that need to be allowed access to various partition information objects and stores the current delimiter value as well; A step to specify the object;
Identifying a particular tenant and / or tenant group at the start of a database session and thus defining said value for each delimiter;
Assigning an isolated database to each tenant and / or tenant group, said database comprising metadata objects, each filtered using said “shared attribute” value and said conditional split flag Steps used to allocate data space for tenants and / or tenant groups;
Writing the delimiter value in a corresponding delimiter column when writing data to the split information object referenced by the delimiter;
Generating a query for retrieving data from the data area assigned to a particular tenant and / or tenant group;
Including a method.   The database includes, in addition to the partition information object, at least one shared object that is accessible by all tenants for at least a read operation regardless of the session parameter and the conditional partition flag value. The method of claim 4.   The “shared attribute” object includes the “shared attribute” along with an indication of whether split data can be used in a shared mode that may have at least one of the two values, “true” or “false”. 5. The method of claim 4, comprising object content and values, wherein a tenant and / or tenant group is identified and current session parameters are set when the database session begins.   When the sharing mode is set to “true” and these tenants call information objects in the database, the current session parameters are ignored, at least for read operations, depending on the program-controlled set of delimiter values. The method of claim 6, wherein access is granted to a random set of entries in the split information object.