Shared key prefix values across objects
A relational database system may receive, from a client, a query for a data object of a first type. The system may be configured to store a plurality of data objects of a second type such that each data object of the second type is associated with a respective data table and a respective value of a key prefix of an object identifier field. The key prefix may result in an upper limit of data objects supportable by the system. The system may determine that the query is indicative of the data object of the first type of a plurality of data objects of the first type that share a key prefix value such that the upper limit is exceeded. The system may identify a result based on determining that the query indicates data object of the first type and return a query response that indicates the result.
1. A method for data processing, comprising:
receiving, at a relational database system, a request to create a data object of a first type, wherein the request includes an entity name corresponding to the data object, the relational database system being configured to store data objects of a second type such that data objects of the second type are associated with a respective data table in the relational database system and a respective value of a key prefix of an object identifier field, the key prefix resulting in an upper limit of data objects supportable by the relational database system;
creating a data table corresponding to the data object at a separate data system, data objects of the first type associated with respective data tables in the separate data system and a same value of the key prefix such that the upper limit is exceeded, and wherein the data object is identifiable from the separate data system based at least in part on the entity name corresponding to the data object;
receiving, from a client at the relational database system, a query for the data object of the first type;
determining that the query is indicative of the data object of the first type
determining, based at least in part on determining that the query is indicative of the data object of the first type, that the data object is stored in a separate data system from the relational database system and associated with the same value of the key prefix;
transmitting, to the separate data system, a request associated with the data object, wherein the request is generated based at least in part on mapping information maintained in the relational database system and including information that is used to differentiate between data objects of the first type stored in the separate data system and sharing the same value of the key prefix;
identifying a result of the query based at least in part on transmitting the request; and
returning, to the client, a query response that indicates the result of the query.
2. The method of claim 1 , wherein identifying the result of the query comprises:
transmitting, to the separate data system, an application programming interface request that is generated based at least in part on an entity identifier included in the query.
3. The method of claim 1 , further comprising:
identifying, based at least in part on determining that the query is indicative of the data object of the first type, entity information corresponding to the data object, wherein the data objects of the first type are associated with the same value of the key prefix but respective entity information and wherein a second data object of the data objects of the second type is associated with a respective key prefix value that corresponds to respective entity information; and
identifying the result of the query based at least in part on the identified entity information for the data object.
4. The method of claim 1 , wherein determining that the query is indicative of the data object of the first type comprises:
identifying that the query includes an object suffix that indicates that the data object is of the first type.
5. An apparatus for data processing, comprising:
a processor;
memory coupled with the processor; and
instructions stored in the memory and executable by the processor to cause the apparatus to:
receive, at a relational database system, a request to create a data object of a first type, wherein the request includes an entity name corresponding to the data object, the relational database system being configured to store data objects of a second type such that data objects of the second type are associated with a respective data table in the relational database system and a respective value of a key prefix of an object identifier field, the key prefix resulting in an upper limit of data objects supportable by the relational database system;
creating a data table corresponding to the data object at a separate data system, data objects of the first type associated with respective data tables in the separate data system and a same value of the key prefix such that the upper limit is exceeded, and wherein the data object is identifiable from the separate data system based at least in part on the entity name corresponding to the data object;
receive, from a client at the relational database system, a query for the data object of the first type;
determine that the query is indicative of the data object of the first type
determine, based at least in part on determining that the query is indicative of the data object of the first type, that the data object is stored in a separate data system from the relational database system and associated with the same value of the key prefix;
transmit, to the separate data system, a request associated with the data object, wherein the request is generated based at least in part on mapping information maintained in the relational database system and including information that is used to differentiate between data objects of the first type stored in the separate data system and sharing the same value of the key prefix;
identify a result of the query based at least in part on transmitting the request; and
return, to the client, a query response that indicates the result of the query.
6. The apparatus of claim 5 , wherein the instructions to identify the result of the query are executable by the processor to cause the apparatus to:
transmit, to the separate data system, an application programming interface request that is generated based at least in part on an entity identifier included in the query.
7. The apparatus of claim 5 , wherein the instructions are further executable by the processor to cause the apparatus to:
identify, based at least in part on determining that the query is indicative of the data object of the first type, entity information corresponding to the data object, wherein the data objects of the first type are associated with the same value of the key prefix but respective entity information and wherein a second data object of the data objects of the second type is associated with a respective key prefix value that corresponds to respective entity information; and
identify the result of the query based at least in part on the identified entity information for the data object.
8. The apparatus of claim 5 , wherein the instructions to determine that the query is indicative of the data object of the first type are executable by the processor to cause the apparatus to:
identify that the query includes an object suffix that indicates that the data object is of the first type.
9. A non-transitory computer-readable medium storing code for data processing, the code comprising instructions executable by a processor to:
receive, at a relational database system, a request to create a data object of a first type, wherein the request includes an entity name corresponding to the data object, the relational database system being configured to store data objects of a second type such that data objects of the second type are associated with a respective data table in the relational database system and a respective value of a key prefix of an object identifier field, the key prefix resulting in an upper limit of data objects supportable by the relational database system;
creating a data table corresponding to the data object at a separate data system, data objects of the first type associated with respective data tables in the separate data system and a same value of the key prefix such that the upper limit is exceeded, and wherein the data object is identifiable from the separate data system based at least in part on the entity name corresponding to the data object;
receive, from a client at the relational database system, a query for the data object of the first type;
determine that the query is indicative of the data object of the first type
determine, based at least in part on determining that the query is indicative of the data object of the first type, that the data object is stored in a separate data system from the relational database system and associated with the same value of the key prefix;
transmit, to the separate data system, a request associated with the data object, wherein the request is generated based at least in part on mapping information maintained in the relational database system and including information that is used to differentiate between data objects of the first type stored in the separate data system and sharing the same value of the key prefix;
identify a result of the query based at least in part on transmitting the request; and
return, to the client, a query response that indicates the result of the query.
10. The non-transitory computer-readable medium of claim 9 , wherein the instructions to identify the result of the query are executable by the processor to:
transmit, to the separate data system, an application programming interface request that is generated based at least in part on an entity identifier included in the query.
11. The non-transitory computer-readable medium of claim 9 , wherein the instructions are further executable by the processor to:
identify, based at least in part on determining that the query is indicative of the data object of the first type, entity information corresponding to the data object, wherein the data objects of the first type are associated with the same value of the key prefix but respective entity information and wherein a second data object of the data objects of the second type is associated with a respective key prefix value that corresponds to respective entity information; and
identify the result of the query based at least in part on the identified entity information for the data object.