Snowflake Inc. patent applications on September 19th, 2024
Patent Applications by Snowflake Inc. on September 19th, 2024
Snowflake Inc.: 2 patent applications
Snowflake Inc. has applied for patents in the areas of G06F8/65 (1), G06F16/21 (1), G06F16/23 (1), G06F16/22 (1), G06F16/2455 (1) G06F8/65 (1), G06F16/2379 (1)
With keywords such as: data, procedure, transaction, version, versioned, call, timestamp, context, table, and new in patent application abstracts.
Patent Applications by Snowflake Inc.
20240311136. LOADING PROCEDURES OF VERSIONED SCHEMA_simplified_abstract_(snowflake inc.)
Inventor(s): Damien Carru of New York NY (US) for snowflake inc., Benoit Dageville of San Mateo CA (US) for snowflake inc., Unmesh Jagtap of San Mateo CA (US) for snowflake inc., Subramanian Muralidhar of Mercer Island WA (US) for snowflake inc., Jan Michael Timmerman of Guelph (CA) for snowflake inc.
IPC Code(s): G06F8/65, G06F16/21
CPC Code(s): G06F8/65
Abstract: a versioned schema of a data platform. a process of maintaining a call stack of executing objects of an application package having a versioned schema includes calling, by a first procedure executed by one or more processors, a second procedure of a versioned application instance, and determining, by the first procedure, a version of the second procedure based on a call context. in response to determining that the version of the second procedure is not in the call context, the first procedure determines a current version of the versioned application package adds the current version to the call context as the version of the second procedure.
20240311369. TRACKING INTERMEDIATE CHANGES IN DATABASE DATA_simplified_abstract_(snowflake inc.)
Inventor(s): Torsten Grabs of San Mateo CA (US) for snowflake inc., Istvan Cseri of Seattle WA (US) for snowflake inc., Benoit Dageville of San Mateo CA (US) for snowflake inc.
IPC Code(s): G06F16/23, G06F16/22, G06F16/2455
CPC Code(s): G06F16/2379
Abstract: systems, methods, and devices for tracking a series of changes to database data are disclosed. a method includes executing a transaction to modify data in a micro-partition of a table of a database by generating a new micro-partition that embodies the transaction. the method includes associating transaction data with the new micro-partition, wherein the transaction data comprises a timestamp when the transaction was fully executed, and further includes associating modification data with the new micro-partition that comprises an indication of one or more rows of the table that were modified by the transaction. the method includes joining the transaction data with the modification data to generate joined data and querying the joined data to determine a listing of intermediate modifications made to the table between a first timestamp and a second timestamp.