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
Sql import may-not be that efficient, when checked with the create statements from the postgresql documentation, and for almost all example it was giving syntax error.
eg:
CREATE TABLE video_sales (
did VARCHAR(40) DEFAULT 'luso films',
number INTEGER DEFAULT 0,
total CASH DEFAULT '$0.0'
);
Sql importer, not considering the second integer property!!
SQL_mulInteger.mp4
JSON importer, when adding a class with "single character", even if it detects 2 types to be imported, it imports only one. Assuming this is caused because, the second type name is created by deleting a character from the object name given by the user.
json_singleCharImportissue.mp4
issue is formatting of the property names:
4.1. when we import 'role_id', it gets converted to roleId, maybe okay, that is how radical does it, but
4.2. when user try to create a new property with name 'role_id', '' is not allowed
4.3. if user wants '' in property name, they have to create it first and then edit it.
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
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
This will be a collection of importer issues.
eg:
SQL_mulInteger.mp4
json_singleCharImportissue.mp4
4.1. when we import 'role_id', it gets converted to roleId, maybe okay, that is how radical does it, but
4.2. when user try to create a new property with name 'role_id', '' is not allowed
4.3. if user wants '' in property name, they have to create it first and then edit it.
Beta Was this translation helpful? Give feedback.
All reactions