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
orientdb {db=TELE09}> SELECT FROM BLACK_LIST;
+----+-----+----------+----------+-----------+
|# |@RID |@CLASS |BLACK_TYPE|in_Black_to|
+----+-----+----------+----------+-----------+
|0 |#29:0|BLACK_LIST|BAD MAN |[#33:0] |
+----+-----+----------+----------+-----------+
1 item(s) found. Query executed in 0.001 sec(s).
orientdb {db=TELE09}> INFO CLASS BLACK_LIST;
! Class 'BLACK_LIST' does not exist in the database 'TELE09'
orientdb {db=TELE09}> INFO CLASS V
CLASS 'V'
Records..............: 0
Default cluster......: v (id=9)
Supported clusters...: v(9), v_1(10), v_2(11), v_3(12)
Cluster selection....: round-robin
Oversize.............: 0.0
Subclasses.........: TELE_NUMBER
Steps to reproduce the problem
Create Calss in Stuido , and Console can SELECT but CAN'T INFO CLASS
After create any new Class in Console , INFO CLASS WILL WORK
The text was updated successfully, but these errors were encountered:
This is a known limitation of current remote protocol: the schema updates are not sent via push messages to the clients, so you have to reload the schema in console with 'reload schema' command.
OrientDB Version, operating system, or hardware.
Operating System
Expected behavior and actual behavior
Steps to reproduce the problem
Create Calss in Stuido , and Console can SELECT but CAN'T INFO CLASS
After create any new Class in Console , INFO CLASS WILL WORK
The text was updated successfully, but these errors were encountered: