When using ABP Suite Load Entity from Database functionality, it looks that it does not support some schema or table names.
The test case has the following [schema].[table] format across the whole database: [SOME_ASSET_DATA].[SOME_SYSTEM_KEY_MAPPING].
Would this kind of format be problematic?
- ABP CLI version: v5.1.4
- ABP Suite version: v5.0.0
- Data Source: MS SQL Server
- Exception message and stack trace: Cannot retrieve tables! Cannot convert table to entity! Object reference not set to an instance of an object.
- Steps to reproduce the issue: Load Entity From Database > Set Connection String > Connect
7 Answer(s)
-
0
-
0
I didn't work with a *.dacpac file. If you explain how can I create the same tables in my oracle server I can solve the issue. send your file or creation scripts to support@abp.io with this support ticket link
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
After generating the script for the entire database and running each piece individually I stumbled upon something I concluded is not supported by the framework:
CREATE TABLE [ASSET_HIERARCHY]( [ASSET_LEVEL] [hierarchyid] NOT NULL, ) ON [PRIMARY]There are official libraries that adds support for this MS SQL type:
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
That's the thing!
The moment that field shows up in the database the whole functionality goes down, so the error shows up and then no table is available to be selected, no column to select/deselect.
I would gladly contribute to the suite project, but I sense that's only available for internals.
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
