Hi, I'm using Postgres and I'd to prevent user delete Customer record if that record alread used in SalesOrder Table. I already defined the foreignkey in SalesOrder as the below code, but there is no happen when I deleted customer. I expected an exception message will be thrown when I delete a customer already used in dependent tables.
b.ToTable(OrderManagmentDbProperties.DbTablePrefix + "SalesOrders", OrderManagmentDbProperties.DbSchema);
b.ConfigureByConvention();
b.Property(x => x.OrderNumber).HasColumnName(nameof(SalesOrder.OrderNumber)).IsRequired().HasMaxLength(SalesOrderConsts.OrderNumberMaxLength);
b.Property(x => x.OrderDate).HasColumnName(nameof(SalesOrder.OrderDate));
b.Property(x => x.Status).HasColumnName(nameof(SalesOrder.Status));
b.Property(x => x.SalesPerson).HasColumnName(nameof(SalesOrder.SalesPerson)).HasMaxLength(SalesOrderConsts.SalesPersonMaxLength);
b.Property(x => x.TotalAmount).HasColumnName(nameof(SalesOrder.TotalAmount));
b.HasOne<Customer>().WithMany().IsRequired().HasForeignKey(x => x.CustomerId).OnDelete(DeleteBehavior.SetNull);
});
Please help me for this issue. Thanks, Dharmar (Han Nguyen)
hi
There are only two websites for your solution:
- API
- Blazor WASM
Since the blazor wasm is a front web app, and there is only a backend app you don't need to use Redis.
Hi Maliming, May I ask you for your advice, which application model will be the best? We should seperate the Auth server or we should combine with HttpApi? Thanks
Hi, I'm using ABP Suite to create an application solution with following options:
Thanks, Dharma (Han Nguyen)
Yes, It's not the issue of ABP I just want to ask if is there any existing solution to use Devexpress Grid instead of Blazorise Grid. Thanks for your link I will try it. Dharma
Maybe this can help :-) In EntityFrameworkCore add ToLower()
.WhereIf(!string.IsNullOrWhiteSpace(filterText), e => e.Name.ToLower().Contains(filterText.ToLower())) .WhereIf(!string.IsNullOrWhiteSpace(name), e => e.Name.ToLower().Contains(name.ToLower()));
Thanks Buckoge
Hi, I tried to create a new collation in Postgres to support case insensitive and create test table with columns associated with this new collation: CREATE COLLATION english_ci ( PROVIDER = 'icu', LOCALE = 'en-US@colStrength=secondary', DETERMINISTIC = FALSE )
But when I search on the page generated by ABP Suite it throw the error:
Do you have any sample to handle for this case?
Hi,
Is there any way to change in code because when creating the solution with ABP its always create postgres case sensitive db as default during run db migration. Can we apply such as ILIKE in ABP generated code for searching?
Thanks
Hi, How we can fix this problem so that user can input data to search regardless of case sensitive. I'm using Abp Suite to generate UI and Service and faced with this issue for the default search on the generated UI. Thanks Dharma (Han Nguyen)
hi
I think this is the setting of the database.
https://docs.aws.amazon.com/dms/latest/sql-server-to-aurora-postgresql-migration-playbook/chap-sql-server-aurora-pg.sql.casesensitivity.html
I don't mean for table name but I mean for the content/data we input to search, for example we have the original data as below: Then I input "blazor" to filter data and nothing can be fitlered: But if I input exactly as data stored in the database "Blazor", the result is ok and can be filtered: