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
Hello 👋
I was wondering what are the allowed types on a SCHEMAFULL table?
I was trying to add a <future> field to such a table but got an error.
Essentially, what I am trying to do is the following:
DEFINE FIELD members ON TABLE group TYPE future VALUE <future> { <-belongs<-user };
Such a field works perfectly well on a SCHEMALESS table but when running the above query I receive the following error: There is a problem with your request. Refer to the documentation for further information.
Edit: not that big of a deal tbh as I can just inline the future when querying as such:
SELECT name, <-belongs<-user AS members FROM group FETCH members;
But would be nice to know if that is at all feasible or not 😄
In any case, SurrealDB is amazing to use already and I can't wait to dive deeper into its capabilities in my projects 😍
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello 👋
I was wondering what are the allowed types on a
SCHEMAFULL
table?I was trying to add a
<future>
field to such a table but got an error.Essentially, what I am trying to do is the following:
Such a field works perfectly well on a
SCHEMALESS
table but when running the above query I receive the following error:There is a problem with your request. Refer to the documentation for further information.
Edit: not that big of a deal tbh as I can just inline the future when querying as such:
But would be nice to know if that is at all feasible or not 😄
In any case, SurrealDB is amazing to use already and I can't wait to dive deeper into its capabilities in my projects 😍
Beta Was this translation helpful? Give feedback.
All reactions