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
I just pushed a fix that solves the NPE, but please consider that changing the type of a property in most cases is not allowed (ie. if there is no natural way to convert from the old type to the new one, eg. from INTEGER to LONG)
Hi @luigidellaquila,
First of all thank you for the quick fix.
I have to disagree with you though on your comment. The ALTER TABLE name ALTER COLUMN column_name SET DATA TYPE data_type is SQL standard and is supported by every SQL DB if the table is empty (otherwise the only solution would be drop the table and re-create). Additionally a lot of SQL DBs support the extension USING in which you can specify how to migrate the data from old type to new type. Incidentally re-typing to a "bigger" type (e.g. INTEGER to LONG) does not require the USING clause at all and will be executed on tables with data (though locking the whole table in the process).
But nevertheless thanks for the quick fix.
OrientDB Version: 3.0.12
Java Version: OpenJDK 64-Bit Server VM 18.9
OS: CentOS Linux release 7.2.1511
Expected behavior
Property type is altered
Actual behavior
java.lang.NullPointerException
Steps to reproduce
Create a class X with property y of type STRING
Enter ALTER PROPERTY X.Y TYPE LINK in Studio
The response is a java.lang.NullPointerException
The text was updated successfully, but these errors were encountered: