realtime dependencies (e.g. T1 com- pletes before T2 begins) in our analysis. TiDB doesn’t formally promise realtime guarantees, but our results hold both with and without those constraints. 1The details of

No one is required to follow them but doing so tends to be to everyone’s advantage. We cannot promise to fix every bug right away. If the bug is obvious, critical, or affects a lot of users, chances choose to do something different. 79 Chapter 7. Queries consequence of the fact that SQL does not promise to deliver the results of a query in any particular order unless ORDER BY is used to constrain the default if the CREATE FUNCTION command does not specify a category. The volatility category is a promise to the optimizer about the behavior of the function: • A VOLATILE function can do anything, including

No one is required to follow them but doing so tends to be to everyone’s advantage. We cannot promise to fix every bug right away. If the bug is obvious, critical, or affects a lot of users, chances ordering with ORDER BY. This is not a bug; it is an inherent consequence of the fact that SQL does not promise to deliver the results of a query in any particular order unless ORDER BY is used to constrain the default if the CREATE FUNCTION command does not specify a cat- egory. The volatility category is a promise to the optimizer about the behavior of the function: • A VOLATILE function can do anything, including

No one is required to follow them but doing so tends to be to everyone’s advantage. We cannot promise to fix every bug right away. If the bug is obvious, critical, or affects a lot of users, chances ordering with ORDER BY. This is not a bug; it is an inherent consequence of the fact that SQL does not promise to deliver the results of a query in any particular order unless ORDER BY is used to constrain the default if the CREATE FUNCTION command does not specify a category. The volatility category is a promise to the optimizer about the behavior of the function: • A VOLATILE function can do anything, including

No one is required to follow them but doing so tends to be to everyone’s advantage. We cannot promise to fix every bug right away. If the bug is obvious, critical, or affects a lot of users, chances ordering with ORDER BY. This is not a bug; it is an inherent consequence of the fact that SQL does not promise to deliver the results of a query in any particular order unless ORDER BY is used to constrain the default if the CREATE FUNCTION command does not specify a category. The volatility category is a promise to the optimizer about the behavior of the function: • A VOLATILE function can do anything, including

No one is required to follow them but doing so tends to be to everyone's advantage. We cannot promise to fix every bug right away. If the bug is obvious, critical, or affects a lot of users, chances ordering with ORDER BY. This is not a bug; it is an inherent consequence of the fact that SQL does not promise to deliver the results of a query in any particular order unless ORDER BY is used to constrain the default if the CREATE FUNCTION command does not specify a category. The volatility category is a promise to the optimizer about the behavior of the function: • A VOLATILE function can do anything, including

No one is required to follow them but doing so tends to be to everyone’s advantage. We cannot promise to fix every bug right away. If the bug is obvious, critical, or affects a lot of users, chances ordering with ORDER BY. This is not a bug; it is an inherent consequence of the fact that SQL does not promise to deliver the results of a query in any particular order unless ORDER BY is used to constrain the default if the CREATE FUNCTION command does not specify a category. The volatility category is a promise to the optimizer about the behavior of the function: • A VOLATILE function can do anything, including

No one is required to follow them but doing so tends to be to everyone’s advantage. We cannot promise to fix every bug right away. If the bug is obvious, critical, or affects a lot of users, chances ordering with ORDER BY. This is not a bug; it is an inherent consequence of the fact that SQL does not promise to deliver the results of a query in any particular order unless ORDER BY is used to constrain the default if the CREATE FUNCTION command does not specify a category. The volatility category is a promise to the optimizer about the behavior of the function: • A VOLATILE function can do anything, including

No one is required to follow them but doing so tends to be to everyone’s advantage. We cannot promise to fix every bug right away. If the bug is obvious, critical, or affects a lot of users, chances ordering with ORDER BY. This is not a bug; it is an inherent consequence of the fact that SQL does not promise to deliver the results of a query in any particular order unless ORDER BY is used to constrain the default if the CREATE FUNCTION command does not specify a category. The volatility category is a promise to the optimizer about the behavior of the function: • A VOLATILE function can do anything, including

No one is required to follow them but doing so tends to be to everyone’s advantage. We cannot promise to fix every bug right away. If the bug is obvious, critical, or affects a lot of users, chances ordering with ORDER BY. This is not a bug; it is an inherent consequence of the fact that SQL does not promise to deliver the results of a query in any particular order unless ORDER BY is used to constrain the command does not specify a 936 Chapter 35. Extending SQL category. The volatility category is a promise to the optimizer about the behavior of the function: • A VOLATILE function can do anything, including