You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The existing docs cover futures, but not how they can be used as part of DEFINE, i.e. DEFINE FIELD first_name ON account TYPE string; on a schemaful table, its unclear how one can achieve the same with a future.
Additionally, the info performance penalty for using futures would be great, the dos / donts and caveats, if any and some examples i.e. how to calculate "birth day" from "date of birth".
Is there an existing issue for this?
I have searched the existing issues
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Description
The existing docs cover futures, but not how they can be used as part of
DEFINE
, i.e.DEFINE FIELD first_name ON account TYPE string;
on a schemaful table, its unclear how one can achieve the same with a future.Additionally, the info performance penalty for using futures would be great, the dos / donts and caveats, if any and some examples i.e. how to calculate "birth day" from "date of birth".
Is there an existing issue for this?
Code of Conduct
The text was updated successfully, but these errors were encountered: