Hello,
I need additional information to understand your problem more clearly. For example, which distributed eventbus provider are you using?
Here are the providers:
LocalDistributedEventBus is the default implementation that implements the distributed event bus to work as in-process. Yes! The default implementation works just like the local event bus, if you don't configure a real distributed provider.AzureDistributedEventBus implements the distributed event bus with the Azure Service Bus. See the Azure Service Bus integration document to learn how to configure it.RabbitMqDistributedEventBus implements the distributed event bus with the RabbitMQ. See the RabbitMQ integration document to learn how to configure it.KafkaDistributedEventBus implements the distributed event bus with the Kafka. See the Kafka integration document to learn how to configure it.RebusDistributedEventBus implements the distributed event bus with the Rebus. See the Rebus integration document to learn how to configure it.Hi,
There are a few questions I would like to ask in order to better answer your question.
Volo.Saas.Domain.Shared reference in MyProjectName.Domain.Shared.csproj in MyProjectName.Domain.Shared project.IsEnabled property in MultiTenancyConsts class in MultiTenancy folder in MyProjectName.Domain.Shared project. This is probably set to false in your case.If so, simply set this value to true and create a new migration. However, if you don't have a reference to the SaaS module, we will need to add the SaaS module first and move on. I can guide you according to your answers.
Hello,
I need additional information to understand your problem more clearly. For example, which distributed eventbus provider are you using?
Here are the providers:
LocalDistributedEventBus is the default implementation that implements the distributed event bus to work as in-process. Yes! The default implementation works just like the local event bus, if you don't configure a real distributed provider.AzureDistributedEventBus implements the distributed event bus with the Azure Service Bus. See the Azure Service Bus integration document to learn how to configure it.RabbitMqDistributedEventBus implements the distributed event bus with the RabbitMQ. See the RabbitMQ integration document to learn how to configure it.KafkaDistributedEventBus implements the distributed event bus with the Kafka. See the Kafka integration document to learn how to configure it.RebusDistributedEventBus implements the distributed event bus with the Rebus. See the Rebus integration document to learn how to configure it..NET tool Volo.Abp.Studio.Cli installation failed. Exit code: 1, Output: Unhandled exception: NuGet.Protocol.Core.Types.FatalProtocolException: Unable to load the service index for source https://packagelibrary.dmssolutionsweb.net/nuget.
Hello, this error seems to be related to your computer configurations. The Volo.Abp.Studio.Cli package has been released on nuget.org and should be publicly available and can be installed without any problems. I suspect there might be a problem in your global NuGet configuration file, you can check this document if you want. I also suggest you take a look here.
Hello,
You can create a new ticket. Thanks
Normally, developer should care if the entity is soft delete and apply index based on it, like b.HasIndex(e => new { e.Name, e.IsDeleted }).IsUnique();
However, this is also not the final solution. Think that you have deleted an entity named "Foo", then created another entity with name "Foo", then you can not delete it since there will be two deleted "Foo" in this case.
I didn't know b.HasIndex(e => e.Name).IsUnique().HasFilter("[IsDeleted] != 1"); usage, but it seems a good solution at least for some databases. However, I think this is not ABP's job and developer should care about it. We may create an extension method for HasFilter("[IsDeleted] != 1") at most and document it.
We agreed that this is not ABP's job and the developer should take care of it.
We are also considering the documentation, but HasFilter(“[IsDeleted] != 1”) is not supported by all databases, so we do not plan to provide such an extension method for now. However, we can provide additional information for those who want to ensure that username or email is unique at the database level, but I am not sure how much it is necessary. Because ABP already guarantees uniqueness at the application level and already covers most scenarios. As a best practice, as you said, it should also be at the database level, but we cannot add it due to the above problems. Nevertheless, we will consider adding it as a note to the document. Thanks for your understanding.
Hi,
You can find the log records on C:\Users\{USERNAME}\.abp\studio\cli\logs.
Hello again, after a short discussion, we agreed on the following opinion:
https://github.com/abpframework/abp/issues/1181#issuecomment-497723988
Thanks ❤️
Thanks for the reply. Of course, we are aware that we can add this protection ourselves, but I opened this topic since ABP is not guaranteeing this behavior ( unique users). I think you should probably update the documentation in this case and let users know that they have to think about this situation.
I will inform the relevant team member to consider this. Thank you for your suggestion.
Regarding what you said with the soft delete and tenancy, in SQL you have filtered indexes, in the sense that you can say that a deleted user is not covered by the unique index ( where IsDeleted = 0 ). Also for multi tenancy, the unique index can be a combination of Username + TenantId.
Yes, I agree, it could be. We can also consider that. As far as I remember, it was already like this in the old versions of ABP, but then we removed it due to some problems.
I am closing this issue for now, but I will definitely share what you said with my teammate and we will inform you here if necessary. Thank you.
