431 lines
119 KiB
Plaintext
431 lines
119 KiB
Plaintext
2024-12-02 15:32:31.918 [INF] --------------------------APPLICATION STARTED---------------------
|
||
2024-12-02 15:32:32.731 [DBG] Hosting starting
|
||
2024-12-02 15:32:32.745 [INF] User profile is available. Using '/Users/preet/.aspnet/DataProtection-Keys' as key repository; keys will not be encrypted at rest.
|
||
2024-12-02 15:32:32.792 [DBG] Reading data from file '/Users/preet/.aspnet/DataProtection-Keys/key-d7860873-b511-456e-9618-1a4a88df185a.xml'.
|
||
2024-12-02 15:32:32.798 [DBG] Found key {d7860873-b511-456e-9618-1a4a88df185a}.
|
||
2024-12-02 15:32:32.805 [DBG] Considering key {d7860873-b511-456e-9618-1a4a88df185a} with expiration date 2025-02-22 20:52:02Z as default key.
|
||
2024-12-02 15:32:32.806 [DBG] Forwarded activator type request from Microsoft.AspNetCore.DataProtection.AuthenticatedEncryption.ConfigurationModel.AuthenticatedEncryptorDescriptorDeserializer, Microsoft.AspNetCore.DataProtection, Version=9.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60 to Microsoft.AspNetCore.DataProtection.AuthenticatedEncryption.ConfigurationModel.AuthenticatedEncryptorDescriptorDeserializer, Microsoft.AspNetCore.DataProtection, Culture=neutral, PublicKeyToken=adb9793829ddae60
|
||
2024-12-02 15:32:32.808 [DBG] Using managed symmetric algorithm 'System.Security.Cryptography.Aes'.
|
||
2024-12-02 15:32:32.808 [DBG] Using managed keyed hash algorithm 'System.Security.Cryptography.HMACSHA256'.
|
||
2024-12-02 15:32:32.809 [DBG] Using key {d7860873-b511-456e-9618-1a4a88df185a} as the default key.
|
||
2024-12-02 15:32:32.809 [DBG] Key ring with default key {d7860873-b511-456e-9618-1a4a88df185a} was loaded during application startup.
|
||
2024-12-02 15:32:32.919 [DBG] Registered model binder providers, in the following order: ["Microsoft.AspNetCore.Mvc.Versioning.ApiVersionModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.BinderTypeModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.ServicesModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.BodyModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.HeaderModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.FloatingPointTypeModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.EnumTypeModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.DateTimeModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.SimpleTypeModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.TryParseModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.CancellationTokenModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.ByteArrayModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.FormFileModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.FormCollectionModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.KeyValuePairModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.DictionaryModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.ArrayModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.CollectionModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.ComplexObjectModelBinderProvider"]
|
||
2024-12-02 15:32:32.944 [WRN] The WebRootPath was not found: /Users/preet/Documents/Odiproject/practicekea_backend/microservices/user/wwwroot. Static files may be unavailable.
|
||
2024-12-02 15:32:32.945 [DBG] Middleware configuration started with options: {AllowedHosts = *, AllowEmptyHosts = True, IncludeFailureMessage = True}
|
||
2024-12-02 15:32:32.947 [DBG] Wildcard detected, all requests with hosts will be allowed.
|
||
2024-12-02 15:32:32.964 [INF] Now listening on: http://localhost:8008
|
||
2024-12-02 15:32:32.964 [DBG] Loaded hosting startup assembly API.User
|
||
2024-12-02 15:32:32.964 [INF] Application started. Press Ctrl+C to shut down.
|
||
2024-12-02 15:32:32.964 [INF] Hosting environment: Development
|
||
2024-12-02 15:32:32.964 [INF] Content root path: /Users/preet/Documents/Odiproject/practicekea_backend/microservices/user
|
||
2024-12-02 15:32:32.964 [DBG] Hosting started
|
||
2024-12-02 15:32:46.327 [DBG] Connection id "0HN8IN1S9OD07" received FIN.
|
||
2024-12-02 15:32:46.342 [DBG] Connection id "0HN8IN1S9OD07" accepted.
|
||
2024-12-02 15:32:46.343 [DBG] Connection id "0HN8IN1S9OD07" started.
|
||
2024-12-02 15:32:46.350 [DBG] Connection id "0HN8IN1S9OD08" accepted.
|
||
2024-12-02 15:32:46.350 [DBG] Connection id "0HN8IN1S9OD08" started.
|
||
2024-12-02 15:32:46.356 [DBG] Connection id "0HN8IN1S9OD07" sending FIN because: "The Socket transport's send loop completed gracefully."
|
||
2024-12-02 15:32:46.360 [DBG] Connection id "0HN8IN1S9OD07" disconnecting.
|
||
2024-12-02 15:32:46.360 [DBG] Connection id "0HN8IN1S9OD07" stopped.
|
||
2024-12-02 15:32:46.375 [INF] Request starting HTTP/1.1 POST http://localhost:8008/v1/Users/SignUpNew - application/json 90
|
||
2024-12-02 15:32:46.376 [DBG] POST requests are not supported
|
||
2024-12-02 15:32:46.376 [DBG] POST requests are not supported
|
||
2024-12-02 15:32:46.396 [DBG] POST requests are not supported
|
||
2024-12-02 15:32:46.411 [DBG] 1 candidate(s) found for the request path '/v1/Users/SignUpNew'
|
||
2024-12-02 15:32:46.413 [DBG] Endpoint 'OnlineAssessment.V1.Controllers.UsersController.SignUpNew (API.User)' with route pattern 'v{version:apiVersion}/Users/SignUpNew' is valid for the request path '/v1/Users/SignUpNew'
|
||
2024-12-02 15:32:46.415 [DBG] Request matched endpoint 'OnlineAssessment.V1.Controllers.UsersController.SignUpNew (API.User)'
|
||
2024-12-02 15:32:47.019 [INF] Failed to validate the token.
|
||
Microsoft.IdentityModel.Tokens.SecurityTokenExpiredException: IDX10223: Lifetime validation failed. The token is expired. ValidTo (UTC): '08/10/2022 8:49:16 AM', Current time (UTC): '02/12/2024 10:02:47 AM'.
|
||
at Microsoft.IdentityModel.Tokens.Validators.ValidateLifetime(Nullable`1 notBefore, Nullable`1 expires, SecurityToken securityToken, TokenValidationParameters validationParameters)
|
||
at Microsoft.IdentityModel.Tokens.InternalValidators.ValidateAfterSignatureFailed(SecurityToken securityToken, Nullable`1 notBefore, Nullable`1 expires, IEnumerable`1 audiences, TokenValidationParameters validationParameters, BaseConfiguration configuration)
|
||
at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateSignature(String token, JwtSecurityToken jwtToken, TokenValidationParameters validationParameters, BaseConfiguration configuration)
|
||
at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateSignatureAndIssuerSecurityKey(String token, JwtSecurityToken jwtToken, TokenValidationParameters validationParameters, BaseConfiguration configuration)
|
||
at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateJWS(String token, TokenValidationParameters validationParameters, BaseConfiguration currentConfiguration, SecurityToken& signatureValidatedToken, ExceptionDispatchInfo& exceptionThrown)
|
||
--- End of stack trace from previous location ---
|
||
at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateToken(String token, JwtSecurityToken outerToken, TokenValidationParameters validationParameters, SecurityToken& signatureValidatedToken)
|
||
at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateToken(String token, TokenValidationParameters validationParameters, SecurityToken& validatedToken)
|
||
at Microsoft.AspNetCore.Authentication.JwtBearer.JwtBearerHandler.HandleAuthenticateAsync()
|
||
2024-12-02 15:32:47.029 [INF] Bearer was not authenticated. Failure message: IDX10223: Lifetime validation failed. The token is expired. ValidTo (UTC): '08/10/2022 8:49:16 AM', Current time (UTC): '02/12/2024 10:02:47 AM'.
|
||
2024-12-02 15:32:47.031 [INF] Executing endpoint 'OnlineAssessment.V1.Controllers.UsersController.SignUpNew (API.User)'
|
||
2024-12-02 15:32:47.042 [INF] Route matched with {action = "SignUpNew", controller = "Users"}. Executing controller action with signature System.Threading.Tasks.Task`1[Microsoft.AspNetCore.Mvc.IActionResult] SignUpNew(OnlineAssessment.Domain.ViewModels.SignupRequestModel) on controller OnlineAssessment.V1.Controllers.UsersController (API.User).
|
||
2024-12-02 15:32:47.042 [DBG] Execution plan of authorization filters (in the following order): ["None"]
|
||
2024-12-02 15:32:47.042 [DBG] Execution plan of resource filters (in the following order): ["None"]
|
||
2024-12-02 15:32:47.043 [DBG] Execution plan of action filters (in the following order): ["Microsoft.AspNetCore.Mvc.ModelBinding.UnsupportedContentTypeFilter (Order: -3000)","Microsoft.AspNetCore.Mvc.Infrastructure.ModelStateInvalidFilter (Order: -2000)","Microsoft.AspNetCore.Mvc.ReportApiVersionsAttribute (Order: 0)"]
|
||
2024-12-02 15:32:47.043 [DBG] Execution plan of exception filters (in the following order): ["None"]
|
||
2024-12-02 15:32:47.043 [DBG] Execution plan of result filters (in the following order): ["Microsoft.AspNetCore.Mvc.Infrastructure.ClientErrorResultFilter (Order: -2000)","Microsoft.AspNetCore.Mvc.ReportApiVersionsAttribute (Order: 0)"]
|
||
2024-12-02 15:32:47.044 [DBG] Executing controller factory for controller OnlineAssessment.V1.Controllers.UsersController (API.User)
|
||
2024-12-02 15:32:47.229 [DBG] Executed controller factory for controller OnlineAssessment.V1.Controllers.UsersController (API.User)
|
||
2024-12-02 15:32:47.238 [DBG] Attempting to bind parameter 'request' of type 'OnlineAssessment.Domain.ViewModels.SignupRequestModel' ...
|
||
2024-12-02 15:32:47.239 [DBG] Attempting to bind parameter 'request' of type 'OnlineAssessment.Domain.ViewModels.SignupRequestModel' using the name '' in request data ...
|
||
2024-12-02 15:32:47.239 [DBG] Rejected input formatter 'Microsoft.AspNetCore.Mvc.Formatters.NewtonsoftJsonPatchInputFormatter' for content type 'application/json'.
|
||
2024-12-02 15:32:47.240 [DBG] Selected input formatter 'Microsoft.AspNetCore.Mvc.Formatters.NewtonsoftJsonInputFormatter' for content type 'application/json'.
|
||
2024-12-02 15:32:47.243 [DBG] Connection id "0HN8IN1S9OD08", Request id "0HN8IN1S9OD08:00000001": started reading request body.
|
||
2024-12-02 15:32:47.244 [DBG] Connection id "0HN8IN1S9OD08", Request id "0HN8IN1S9OD08:00000001": done reading request body.
|
||
2024-12-02 15:32:47.250 [DBG] Done attempting to bind parameter 'request' of type 'OnlineAssessment.Domain.ViewModels.SignupRequestModel'.
|
||
2024-12-02 15:32:47.250 [DBG] Done attempting to bind parameter 'request' of type 'OnlineAssessment.Domain.ViewModels.SignupRequestModel'.
|
||
2024-12-02 15:32:47.250 [DBG] Attempting to validate the bound parameter 'request' of type 'OnlineAssessment.Domain.ViewModels.SignupRequestModel' ...
|
||
2024-12-02 15:32:47.255 [DBG] Done attempting to validate the bound parameter 'request' of type 'OnlineAssessment.Domain.ViewModels.SignupRequestModel'.
|
||
2024-12-02 15:32:48.823 [DBG] No relationship from 'OrderPayment' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation', 'UpdatedByNavigation', 'User'} that could be matched with the properties on the other entity type - {'OrderPaymentCreatedByNavigation', 'OrderPaymentUpdatedByNavigation', 'OrderPaymentUser'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:48.829 [DBG] No relationship from 'Orders' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation', 'UpdatedByNavigation'} that could be matched with the properties on the other entity type - {'OrdersCreatedByNavigation', 'OrdersUpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:48.833 [DBG] No relationship from 'PracticeAttempts' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation', 'UpdatedByNavigation'} that could be matched with the properties on the other entity type - {'PracticeAttemptsCreatedByNavigation', 'PracticeAttemptsUpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:48.835 [DBG] No relationship from 'Practices' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation', 'UpdatedByNavigation'} that could be matched with the properties on the other entity type - {'PracticesCreatedByNavigation', 'PracticesUpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:48.836 [DBG] No relationship from 'QuestionBugs' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation', 'UpdatedByNavigation'} that could be matched with the properties on the other entity type - {'QuestionBugsCreatedByNavigation', 'QuestionBugsUpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:48.845 [DBG] No relationship from 'SubscribedExams' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation', 'UpdatedByNavigation'} that could be matched with the properties on the other entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:48.846 [DBG] No relationship from 'SubscribedPractices' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation', 'UpdatedByNavigation'} that could be matched with the properties on the other entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:48.856 [DBG] No relationship from 'Users' to 'OrderPayment' has been configured by convention because there are multiple properties on one entity type - {'OrderPaymentCreatedByNavigation', 'OrderPaymentUpdatedByNavigation', 'OrderPaymentUser'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation', 'User'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:48.856 [DBG] No relationship from 'Users' to 'Orders' has been configured by convention because there are multiple properties on one entity type - {'OrdersCreatedByNavigation', 'OrdersUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:48.856 [DBG] No relationship from 'Users' to 'PracticeAttempts' has been configured by convention because there are multiple properties on one entity type - {'PracticeAttemptsCreatedByNavigation', 'PracticeAttemptsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:48.856 [DBG] No relationship from 'Users' to 'Practices' has been configured by convention because there are multiple properties on one entity type - {'PracticesCreatedByNavigation', 'PracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:48.856 [DBG] No relationship from 'Users' to 'QuestionBugs' has been configured by convention because there are multiple properties on one entity type - {'QuestionBugsCreatedByNavigation', 'QuestionBugsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:48.856 [DBG] No relationship from 'Users' to 'SubscribedExams' has been configured by convention because there are multiple properties on one entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:48.856 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.114 [DBG] No relationship from 'OrderPayment' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation', 'UpdatedByNavigation', 'User'} that could be matched with the properties on the other entity type - {'OrderPaymentCreatedByNavigation', 'OrderPaymentUpdatedByNavigation', 'OrderPaymentUser'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.115 [DBG] No relationship from 'Users' to 'OrderPayment' has been configured by convention because there are multiple properties on one entity type - {'OrderPaymentCreatedByNavigation', 'OrderPaymentUpdatedByNavigation', 'OrderPaymentUser'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation', 'User'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.115 [DBG] No relationship from 'Users' to 'Orders' has been configured by convention because there are multiple properties on one entity type - {'OrdersCreatedByNavigation', 'OrdersUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.115 [DBG] No relationship from 'Users' to 'PracticeAttempts' has been configured by convention because there are multiple properties on one entity type - {'PracticeAttemptsCreatedByNavigation', 'PracticeAttemptsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.115 [DBG] No relationship from 'Users' to 'Practices' has been configured by convention because there are multiple properties on one entity type - {'PracticesCreatedByNavigation', 'PracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.115 [DBG] No relationship from 'Users' to 'QuestionBugs' has been configured by convention because there are multiple properties on one entity type - {'QuestionBugsCreatedByNavigation', 'QuestionBugsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.115 [DBG] No relationship from 'Users' to 'SubscribedExams' has been configured by convention because there are multiple properties on one entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.115 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.117 [DBG] No relationship from 'Users' to 'OrderPayment' has been configured by convention because there are multiple properties on one entity type - {'OrderPaymentUpdatedByNavigation', 'OrderPaymentUser'} that could be matched with the properties on the other entity type - {'UpdatedByNavigation', 'User'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.117 [DBG] No relationship from 'Users' to 'Orders' has been configured by convention because there are multiple properties on one entity type - {'OrdersCreatedByNavigation', 'OrdersUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.117 [DBG] No relationship from 'Users' to 'PracticeAttempts' has been configured by convention because there are multiple properties on one entity type - {'PracticeAttemptsCreatedByNavigation', 'PracticeAttemptsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.117 [DBG] No relationship from 'Users' to 'Practices' has been configured by convention because there are multiple properties on one entity type - {'PracticesCreatedByNavigation', 'PracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.117 [DBG] No relationship from 'Users' to 'QuestionBugs' has been configured by convention because there are multiple properties on one entity type - {'QuestionBugsCreatedByNavigation', 'QuestionBugsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.117 [DBG] No relationship from 'Users' to 'SubscribedExams' has been configured by convention because there are multiple properties on one entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.117 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.117 [DBG] No relationship from 'OrderPayment' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation'} that could be matched with the properties on the other entity type - {'OrderPaymentCreatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.117 [DBG] No relationship from 'OrderPayment' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'UpdatedByNavigation', 'User'} that could be matched with the properties on the other entity type - {'OrderPaymentUpdatedByNavigation', 'OrderPaymentUser'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.120 [DBG] No relationship from 'OrderPayment' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'UpdatedByNavigation', 'User'} that could be matched with the properties on the other entity type - {'OrderPaymentUpdatedByNavigation', 'OrderPaymentUser'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.120 [DBG] No relationship from 'Users' to 'OrderPayment' has been configured by convention because there are multiple properties on one entity type - {'OrderPaymentCreatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.120 [DBG] No relationship from 'Users' to 'OrderPayment' has been configured by convention because there are multiple properties on one entity type - {'OrderPaymentUpdatedByNavigation', 'OrderPaymentUser'} that could be matched with the properties on the other entity type - {'UpdatedByNavigation', 'User'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.120 [DBG] No relationship from 'Users' to 'Orders' has been configured by convention because there are multiple properties on one entity type - {'OrdersCreatedByNavigation', 'OrdersUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.120 [DBG] No relationship from 'Users' to 'PracticeAttempts' has been configured by convention because there are multiple properties on one entity type - {'PracticeAttemptsCreatedByNavigation', 'PracticeAttemptsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.120 [DBG] No relationship from 'Users' to 'Practices' has been configured by convention because there are multiple properties on one entity type - {'PracticesCreatedByNavigation', 'PracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.120 [DBG] No relationship from 'Users' to 'QuestionBugs' has been configured by convention because there are multiple properties on one entity type - {'QuestionBugsCreatedByNavigation', 'QuestionBugsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.121 [DBG] No relationship from 'Users' to 'SubscribedExams' has been configured by convention because there are multiple properties on one entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.121 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.122 [DBG] No relationship from 'Users' to 'Orders' has been configured by convention because there are multiple properties on one entity type - {'OrdersCreatedByNavigation', 'OrdersUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.122 [DBG] No relationship from 'Users' to 'PracticeAttempts' has been configured by convention because there are multiple properties on one entity type - {'PracticeAttemptsCreatedByNavigation', 'PracticeAttemptsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.122 [DBG] No relationship from 'Users' to 'Practices' has been configured by convention because there are multiple properties on one entity type - {'PracticesCreatedByNavigation', 'PracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.122 [DBG] No relationship from 'Users' to 'QuestionBugs' has been configured by convention because there are multiple properties on one entity type - {'QuestionBugsCreatedByNavigation', 'QuestionBugsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.122 [DBG] No relationship from 'Users' to 'SubscribedExams' has been configured by convention because there are multiple properties on one entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.122 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.127 [DBG] No relationship from 'Orders' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation', 'UpdatedByNavigation'} that could be matched with the properties on the other entity type - {'OrdersCreatedByNavigation', 'OrdersUpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.127 [DBG] No relationship from 'Users' to 'Orders' has been configured by convention because there are multiple properties on one entity type - {'OrdersCreatedByNavigation', 'OrdersUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.128 [DBG] No relationship from 'Users' to 'PracticeAttempts' has been configured by convention because there are multiple properties on one entity type - {'PracticeAttemptsCreatedByNavigation', 'PracticeAttemptsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.128 [DBG] No relationship from 'Users' to 'Practices' has been configured by convention because there are multiple properties on one entity type - {'PracticesCreatedByNavigation', 'PracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.128 [DBG] No relationship from 'Users' to 'QuestionBugs' has been configured by convention because there are multiple properties on one entity type - {'QuestionBugsCreatedByNavigation', 'QuestionBugsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.128 [DBG] No relationship from 'Users' to 'SubscribedExams' has been configured by convention because there are multiple properties on one entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.128 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.129 [DBG] No relationship from 'Users' to 'PracticeAttempts' has been configured by convention because there are multiple properties on one entity type - {'PracticeAttemptsCreatedByNavigation', 'PracticeAttemptsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.129 [DBG] No relationship from 'Users' to 'Practices' has been configured by convention because there are multiple properties on one entity type - {'PracticesCreatedByNavigation', 'PracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.129 [DBG] No relationship from 'Users' to 'QuestionBugs' has been configured by convention because there are multiple properties on one entity type - {'QuestionBugsCreatedByNavigation', 'QuestionBugsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.129 [DBG] No relationship from 'Users' to 'SubscribedExams' has been configured by convention because there are multiple properties on one entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.129 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.140 [DBG] No relationship from 'PracticeAttempts' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation', 'UpdatedByNavigation'} that could be matched with the properties on the other entity type - {'PracticeAttemptsCreatedByNavigation', 'PracticeAttemptsUpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.141 [DBG] No relationship from 'Users' to 'PracticeAttempts' has been configured by convention because there are multiple properties on one entity type - {'PracticeAttemptsCreatedByNavigation', 'PracticeAttemptsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.141 [DBG] No relationship from 'Users' to 'Practices' has been configured by convention because there are multiple properties on one entity type - {'PracticesCreatedByNavigation', 'PracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.141 [DBG] No relationship from 'Users' to 'QuestionBugs' has been configured by convention because there are multiple properties on one entity type - {'QuestionBugsCreatedByNavigation', 'QuestionBugsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.141 [DBG] No relationship from 'Users' to 'SubscribedExams' has been configured by convention because there are multiple properties on one entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.141 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.142 [DBG] No relationship from 'Users' to 'Practices' has been configured by convention because there are multiple properties on one entity type - {'PracticesCreatedByNavigation', 'PracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.142 [DBG] No relationship from 'Users' to 'QuestionBugs' has been configured by convention because there are multiple properties on one entity type - {'QuestionBugsCreatedByNavigation', 'QuestionBugsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.142 [DBG] No relationship from 'Users' to 'SubscribedExams' has been configured by convention because there are multiple properties on one entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.142 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.150 [DBG] No relationship from 'Practices' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation', 'UpdatedByNavigation'} that could be matched with the properties on the other entity type - {'PracticesCreatedByNavigation', 'PracticesUpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.151 [DBG] No relationship from 'Users' to 'Practices' has been configured by convention because there are multiple properties on one entity type - {'PracticesCreatedByNavigation', 'PracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.151 [DBG] No relationship from 'Users' to 'QuestionBugs' has been configured by convention because there are multiple properties on one entity type - {'QuestionBugsCreatedByNavigation', 'QuestionBugsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.151 [DBG] No relationship from 'Users' to 'SubscribedExams' has been configured by convention because there are multiple properties on one entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.151 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.152 [DBG] No relationship from 'Users' to 'QuestionBugs' has been configured by convention because there are multiple properties on one entity type - {'QuestionBugsCreatedByNavigation', 'QuestionBugsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.152 [DBG] No relationship from 'Users' to 'SubscribedExams' has been configured by convention because there are multiple properties on one entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.152 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.158 [DBG] No relationship from 'QuestionBugs' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation', 'UpdatedByNavigation'} that could be matched with the properties on the other entity type - {'QuestionBugsCreatedByNavigation', 'QuestionBugsUpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.159 [DBG] No relationship from 'Users' to 'QuestionBugs' has been configured by convention because there are multiple properties on one entity type - {'QuestionBugsCreatedByNavigation', 'QuestionBugsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.159 [DBG] No relationship from 'Users' to 'SubscribedExams' has been configured by convention because there are multiple properties on one entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.159 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.160 [DBG] No relationship from 'Users' to 'SubscribedExams' has been configured by convention because there are multiple properties on one entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.160 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.185 [DBG] No relationship from 'SubscribedExams' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation', 'UpdatedByNavigation'} that could be matched with the properties on the other entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.185 [DBG] No relationship from 'Users' to 'SubscribedExams' has been configured by convention because there are multiple properties on one entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.185 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.187 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.191 [DBG] No relationship from 'SubscribedPractices' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation', 'UpdatedByNavigation'} that could be matched with the properties on the other entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.192 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 15:32:49.236 [DBG] The index {'SubjectId'} was not created on entity type 'Categories' as the properties are already covered by the index {'SubjectId', 'Name', 'IsActive'}.
|
||
2024-12-02 15:32:49.236 [DBG] The index {'InstituteId'} was not created on entity type 'Classes' as the properties are already covered by the index {'InstituteId', 'Name', 'IsActive'}.
|
||
2024-12-02 15:32:49.236 [DBG] The index {'ExamId'} was not created on entity type 'ExamSections' as the properties are already covered by the index {'ExamId', 'SubjectId', 'IsActive'}.
|
||
2024-12-02 15:32:49.236 [DBG] The index {'QuestionId'} was not created on entity type 'QuestionCategories' as the properties are already covered by the index {'QuestionId', 'CategoryId', 'IsActive'}.
|
||
2024-12-02 15:32:49.236 [DBG] The index {'QuestionId'} was not created on entity type 'QuestionLanguges' as the properties are already covered by the index {'QuestionId', 'LanguageId', 'IsActive'}.
|
||
2024-12-02 15:32:49.236 [DBG] The index {'QuestionOptionId'} was not created on entity type 'QuestionOptionLanguages' as the properties are already covered by the index {'QuestionOptionId', 'LanguageId', 'IsActive'}.
|
||
2024-12-02 15:32:49.236 [DBG] The index {'QuestionId'} was not created on entity type 'QuestionTags' as the properties are already covered by the index {'QuestionId', 'TagId', 'IsActive'}.
|
||
2024-12-02 15:32:49.236 [DBG] The index {'ClassId'} was not created on entity type 'Subjects' as the properties are already covered by the index {'ClassId', 'Name', 'IsActive'}.
|
||
2024-12-02 15:32:49.237 [DBG] The index {'UserGroupId'} was not created on entity type 'UserGroupMembers' as the properties are already covered by the index {'UserGroupId', 'UserId', 'IsActive'}.
|
||
2024-12-02 15:32:49.237 [DBG] The index {'ClassId'} was not created on entity type 'UserGroups' as the properties are already covered by the index {'ClassId', 'Name', 'IsActive'}.
|
||
2024-12-02 15:32:49.237 [DBG] The index {'InstituteId'} was not created on entity type 'Users' as the properties are already covered by the index {'InstituteId', 'EmailId'}.
|
||
2024-12-02 15:32:49.479 [DBG] Entity Framework Core 9.0.0 initialized 'OnlineAssessmentContext' using provider 'Microsoft.EntityFrameworkCore.SqlServer:9.0.0' with options: MaxPoolSize=1024 EngineType=SqlServer
|
||
2024-12-02 15:32:49.484 [DBG] Creating DbConnection.
|
||
2024-12-02 15:32:49.506 [DBG] Created DbConnection. (21ms).
|
||
2024-12-02 15:32:49.508 [DBG] Opening connection to database 'odiproj1_oa' on server '68.71.130.74,1533'.
|
||
2024-12-02 15:32:51.182 [DBG] Opened connection to database 'odiproj1_oa' on server '68.71.130.74,1533'.
|
||
2024-12-02 15:32:51.184 [DBG] Beginning transaction with isolation level 'Unspecified'.
|
||
2024-12-02 15:32:51.489 [DBG] Began transaction with isolation level 'ReadCommitted'.
|
||
2024-12-02 15:32:51.528 [DBG] 'OnlineAssessmentContext' generated a temporary value for the property 'Users.Id'. Consider using 'DbContextOptionsBuilder.EnableSensitiveDataLogging' to see key values.
|
||
2024-12-02 15:32:51.609 [DBG] Context 'OnlineAssessmentContext' started tracking 'Users' entity. Consider using 'DbContextOptionsBuilder.EnableSensitiveDataLogging' to see key values.
|
||
2024-12-02 15:32:51.610 [DBG] SaveChanges starting for 'OnlineAssessmentContext'.
|
||
2024-12-02 15:32:51.612 [DBG] DetectChanges starting for 'OnlineAssessmentContext'.
|
||
2024-12-02 15:32:51.623 [DBG] DetectChanges completed for 'OnlineAssessmentContext'.
|
||
2024-12-02 15:32:51.708 [DBG] Creating transaction savepoint.
|
||
2024-12-02 15:32:51.997 [DBG] Created transaction savepoint.
|
||
2024-12-02 15:32:52.000 [DBG] Creating DbCommand for 'ExecuteReader'.
|
||
2024-12-02 15:32:52.002 [DBG] Created DbCommand for 'ExecuteReader' (0ms).
|
||
2024-12-02 15:32:52.007 [DBG] Initialized DbCommand for 'ExecuteReader' (7ms).
|
||
2024-12-02 15:32:52.011 [DBG] Executing DbCommand [Parameters=[@p0='?' (Size = 100), @p1='?' (Size = 1500) (DbType = AnsiString), @p2='?' (DbType = Int32), @p3='?' (Size = 1500) (DbType = AnsiString), @p4='?' (Size = 1500) (DbType = AnsiString), @p5='?' (DbType = Int32), @p6='?' (DbType = DateTime), @p7='?' (DbType = Date), @p8='?' (Size = 500) (DbType = AnsiString), @p9='?' (Size = 50), @p10='?' (Size = 10) (DbType = AnsiString), @p11='?' (DbType = Int32), @p12='?' (DbType = Boolean), @p13='?' (DbType = Int32), @p14='?' (Size = 50) (DbType = AnsiString), @p15='?' (Size = 20) (DbType = AnsiString), @p16='?' (Size = 20) (DbType = AnsiString), @p17='?' (Size = 10) (DbType = AnsiString), @p18='?' (Size = 1000) (DbType = AnsiString), @p19='?' (Size = 6) (DbType = AnsiString), @p20='?' (DbType = DateTime), @p21='?' (DbType = Int32), @p22='?' (DbType = Int32), @p23='?' (Size = 50) (DbType = AnsiString), @p24='?' (DbType = Int32), @p25='?' (DbType = DateTime), @p26='?' (Size = 500), @p27='?' (Size = 10) (DbType = AnsiString), @p28='?' (Size = 512)], CommandType='"Text"', CommandTimeout='30']
|
||
SET IMPLICIT_TRANSACTIONS OFF;
|
||
SET NOCOUNT ON;
|
||
INSERT INTO [dbo].[Users] ([access_token], [address], [batch_id], [city], [country], [created_by], [created_on], [date_of_birth], [email_id], [first_name], [gender], [institute_id], [is_active], [language_id], [last_name], [latitude], [longitude], [mobile_no], [photo], [pin_code], [registration_datetime], [registration_id], [role_id], [state_code], [updated_by], [updated_on], [user_password], [user_salt], [uuid])
|
||
OUTPUT INSERTED.[id]
|
||
VALUES (@p0, @p1, @p2, @p3, @p4, @p5, @p6, @p7, @p8, @p9, @p10, @p11, @p12, @p13, @p14, @p15, @p16, @p17, @p18, @p19, @p20, @p21, @p22, @p23, @p24, @p25, @p26, @p27, @p28);
|
||
2024-12-02 15:32:52.309 [INF] Executed DbCommand (292ms) [Parameters=[@p0='?' (Size = 100), @p1='?' (Size = 1500) (DbType = AnsiString), @p2='?' (DbType = Int32), @p3='?' (Size = 1500) (DbType = AnsiString), @p4='?' (Size = 1500) (DbType = AnsiString), @p5='?' (DbType = Int32), @p6='?' (DbType = DateTime), @p7='?' (DbType = Date), @p8='?' (Size = 500) (DbType = AnsiString), @p9='?' (Size = 50), @p10='?' (Size = 10) (DbType = AnsiString), @p11='?' (DbType = Int32), @p12='?' (DbType = Boolean), @p13='?' (DbType = Int32), @p14='?' (Size = 50) (DbType = AnsiString), @p15='?' (Size = 20) (DbType = AnsiString), @p16='?' (Size = 20) (DbType = AnsiString), @p17='?' (Size = 10) (DbType = AnsiString), @p18='?' (Size = 1000) (DbType = AnsiString), @p19='?' (Size = 6) (DbType = AnsiString), @p20='?' (DbType = DateTime), @p21='?' (DbType = Int32), @p22='?' (DbType = Int32), @p23='?' (Size = 50) (DbType = AnsiString), @p24='?' (DbType = Int32), @p25='?' (DbType = DateTime), @p26='?' (Size = 500), @p27='?' (Size = 10) (DbType = AnsiString), @p28='?' (Size = 512)], CommandType='"Text"', CommandTimeout='30']
|
||
SET IMPLICIT_TRANSACTIONS OFF;
|
||
SET NOCOUNT ON;
|
||
INSERT INTO [dbo].[Users] ([access_token], [address], [batch_id], [city], [country], [created_by], [created_on], [date_of_birth], [email_id], [first_name], [gender], [institute_id], [is_active], [language_id], [last_name], [latitude], [longitude], [mobile_no], [photo], [pin_code], [registration_datetime], [registration_id], [role_id], [state_code], [updated_by], [updated_on], [user_password], [user_salt], [uuid])
|
||
OUTPUT INSERTED.[id]
|
||
VALUES (@p0, @p1, @p2, @p3, @p4, @p5, @p6, @p7, @p8, @p9, @p10, @p11, @p12, @p13, @p14, @p15, @p16, @p17, @p18, @p19, @p20, @p21, @p22, @p23, @p24, @p25, @p26, @p27, @p28);
|
||
2024-12-02 15:32:52.319 [DBG] The foreign key property 'Users.Id' was detected as changed. Consider using 'DbContextOptionsBuilder.EnableSensitiveDataLogging' to see property values.
|
||
2024-12-02 15:32:52.325 [DBG] Closing data reader to 'odiproj1_oa' on server '68.71.130.74,1533'.
|
||
2024-12-02 15:32:52.329 [DBG] A data reader for 'odiproj1_oa' on server '68.71.130.74,1533' is being disposed after spending 17ms reading results.
|
||
2024-12-02 15:32:52.335 [DBG] An entity of type 'Users' tracked by 'OnlineAssessmentContext' changed state from '"Added"' to '"Unchanged"'. Consider using 'DbContextOptionsBuilder.EnableSensitiveDataLogging' to see key values.
|
||
2024-12-02 15:32:52.336 [DBG] SaveChanges completed for 'OnlineAssessmentContext' with 1 entities written to the database.
|
||
2024-12-02 15:32:52.336 [DBG] Committing transaction.
|
||
2024-12-02 15:32:52.612 [DBG] Committed transaction.
|
||
2024-12-02 15:32:52.613 [DBG] Closing connection to database 'odiproj1_oa' on server '68.71.130.74,1533'.
|
||
2024-12-02 15:32:52.616 [DBG] Closed connection to database 'odiproj1_oa' on server '68.71.130.74,1533' (3ms).
|
||
2024-12-02 15:33:41.301 [DBG] List of registered output formatters, in the following order: ["Microsoft.AspNetCore.Mvc.Formatters.HttpNoContentOutputFormatter","Microsoft.AspNetCore.Mvc.Formatters.StringOutputFormatter","Microsoft.AspNetCore.Mvc.Formatters.StreamOutputFormatter","Microsoft.AspNetCore.Mvc.Formatters.NewtonsoftJsonOutputFormatter"]
|
||
2024-12-02 15:33:41.303 [DBG] No information found on request to perform content negotiation.
|
||
2024-12-02 15:33:41.303 [DBG] Attempting to select an output formatter without using a content type as no explicit content types were specified for the response.
|
||
2024-12-02 15:33:41.303 [DBG] Attempting to select the first formatter in the output formatters list which can write the result.
|
||
2024-12-02 15:33:41.303 [DBG] Selected output formatter 'Microsoft.AspNetCore.Mvc.Formatters.NewtonsoftJsonOutputFormatter' and content type 'application/json' to write the response.
|
||
2024-12-02 15:33:41.304 [INF] Executing OkObjectResult, writing value of type 'OnlineAssessment.Common.ReturnResponse'.
|
||
2024-12-02 15:33:41.316 [INF] Executed action OnlineAssessment.V1.Controllers.UsersController.SignUpNew (API.User) in 54270.5461ms
|
||
2024-12-02 15:33:41.318 [INF] Executed endpoint 'OnlineAssessment.V1.Controllers.UsersController.SignUpNew (API.User)'
|
||
2024-12-02 15:33:41.321 [INF] HTTP POST /v1/Users/SignUpNew responded 200 in 54942.5168 ms
|
||
2024-12-02 15:33:41.323 [DBG] Connection id "0HN8IN1S9OD08" completed keep alive response.
|
||
2024-12-02 15:33:41.330 [INF] Request finished HTTP/1.1 POST http://localhost:8008/v1/Users/SignUpNew - 200 249 application/json; charset=utf-8 54955.7593ms
|
||
2024-12-02 16:01:30.077 [INF] --------------------------APPLICATION STARTED---------------------
|
||
2024-12-02 16:01:30.962 [DBG] Hosting starting
|
||
2024-12-02 16:01:30.977 [INF] User profile is available. Using '/Users/preet/.aspnet/DataProtection-Keys' as key repository; keys will not be encrypted at rest.
|
||
2024-12-02 16:01:31.031 [DBG] Reading data from file '/Users/preet/.aspnet/DataProtection-Keys/key-d7860873-b511-456e-9618-1a4a88df185a.xml'.
|
||
2024-12-02 16:01:31.111 [DBG] Found key {d7860873-b511-456e-9618-1a4a88df185a}.
|
||
2024-12-02 16:01:31.120 [DBG] Considering key {d7860873-b511-456e-9618-1a4a88df185a} with expiration date 2025-02-22 20:52:02Z as default key.
|
||
2024-12-02 16:01:31.121 [DBG] Forwarded activator type request from Microsoft.AspNetCore.DataProtection.AuthenticatedEncryption.ConfigurationModel.AuthenticatedEncryptorDescriptorDeserializer, Microsoft.AspNetCore.DataProtection, Version=9.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60 to Microsoft.AspNetCore.DataProtection.AuthenticatedEncryption.ConfigurationModel.AuthenticatedEncryptorDescriptorDeserializer, Microsoft.AspNetCore.DataProtection, Culture=neutral, PublicKeyToken=adb9793829ddae60
|
||
2024-12-02 16:01:31.124 [DBG] Using managed symmetric algorithm 'System.Security.Cryptography.Aes'.
|
||
2024-12-02 16:01:31.124 [DBG] Using managed keyed hash algorithm 'System.Security.Cryptography.HMACSHA256'.
|
||
2024-12-02 16:01:31.125 [DBG] Using key {d7860873-b511-456e-9618-1a4a88df185a} as the default key.
|
||
2024-12-02 16:01:31.125 [DBG] Key ring with default key {d7860873-b511-456e-9618-1a4a88df185a} was loaded during application startup.
|
||
2024-12-02 16:01:31.259 [DBG] Registered model binder providers, in the following order: ["Microsoft.AspNetCore.Mvc.Versioning.ApiVersionModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.BinderTypeModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.ServicesModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.BodyModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.HeaderModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.FloatingPointTypeModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.EnumTypeModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.DateTimeModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.SimpleTypeModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.TryParseModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.CancellationTokenModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.ByteArrayModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.FormFileModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.FormCollectionModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.KeyValuePairModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.DictionaryModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.ArrayModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.CollectionModelBinderProvider","Microsoft.AspNetCore.Mvc.ModelBinding.Binders.ComplexObjectModelBinderProvider"]
|
||
2024-12-02 16:01:31.283 [WRN] The WebRootPath was not found: /Users/preet/Documents/Odiproject/practicekea_backend/microservices/user/wwwroot. Static files may be unavailable.
|
||
2024-12-02 16:01:31.284 [DBG] Middleware configuration started with options: {AllowedHosts = *, AllowEmptyHosts = True, IncludeFailureMessage = True}
|
||
2024-12-02 16:01:31.285 [DBG] Wildcard detected, all requests with hosts will be allowed.
|
||
2024-12-02 16:01:31.302 [INF] Now listening on: http://localhost:8008
|
||
2024-12-02 16:01:31.302 [DBG] Loaded hosting startup assembly API.User
|
||
2024-12-02 16:01:31.302 [INF] Application started. Press Ctrl+C to shut down.
|
||
2024-12-02 16:01:31.302 [INF] Hosting environment: Development
|
||
2024-12-02 16:01:31.302 [INF] Content root path: /Users/preet/Documents/Odiproject/practicekea_backend/microservices/user
|
||
2024-12-02 16:01:31.302 [DBG] Hosting started
|
||
2024-12-02 16:01:42.217 [DBG] Connection id "0HN8INI1KG6EB" received FIN.
|
||
2024-12-02 16:01:42.221 [DBG] Connection id "0HN8INI1KG6EB" accepted.
|
||
2024-12-02 16:01:42.222 [DBG] Connection id "0HN8INI1KG6EB" started.
|
||
2024-12-02 16:01:42.228 [DBG] Connection id "0HN8INI1KG6EC" accepted.
|
||
2024-12-02 16:01:42.228 [DBG] Connection id "0HN8INI1KG6EC" started.
|
||
2024-12-02 16:01:42.234 [DBG] Connection id "0HN8INI1KG6EB" sending FIN because: "The Socket transport's send loop completed gracefully."
|
||
2024-12-02 16:01:42.238 [DBG] Connection id "0HN8INI1KG6EB" disconnecting.
|
||
2024-12-02 16:01:42.239 [DBG] Connection id "0HN8INI1KG6EB" stopped.
|
||
2024-12-02 16:01:42.252 [INF] Request starting HTTP/1.1 POST http://localhost:8008/v1/Users/SignUpNew - application/json 90
|
||
2024-12-02 16:01:42.253 [DBG] POST requests are not supported
|
||
2024-12-02 16:01:42.253 [DBG] POST requests are not supported
|
||
2024-12-02 16:01:42.271 [DBG] POST requests are not supported
|
||
2024-12-02 16:01:42.285 [DBG] 1 candidate(s) found for the request path '/v1/Users/SignUpNew'
|
||
2024-12-02 16:01:42.287 [DBG] Endpoint 'OnlineAssessment.V1.Controllers.UsersController.SignUpNew (API.User)' with route pattern 'v{version:apiVersion}/Users/SignUpNew' is valid for the request path '/v1/Users/SignUpNew'
|
||
2024-12-02 16:01:42.290 [DBG] Request matched endpoint 'OnlineAssessment.V1.Controllers.UsersController.SignUpNew (API.User)'
|
||
2024-12-02 16:01:42.898 [INF] Failed to validate the token.
|
||
Microsoft.IdentityModel.Tokens.SecurityTokenExpiredException: IDX10223: Lifetime validation failed. The token is expired. ValidTo (UTC): '08/10/2022 8:49:16 AM', Current time (UTC): '02/12/2024 10:31:42 AM'.
|
||
at Microsoft.IdentityModel.Tokens.Validators.ValidateLifetime(Nullable`1 notBefore, Nullable`1 expires, SecurityToken securityToken, TokenValidationParameters validationParameters)
|
||
at Microsoft.IdentityModel.Tokens.InternalValidators.ValidateAfterSignatureFailed(SecurityToken securityToken, Nullable`1 notBefore, Nullable`1 expires, IEnumerable`1 audiences, TokenValidationParameters validationParameters, BaseConfiguration configuration)
|
||
at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateSignature(String token, JwtSecurityToken jwtToken, TokenValidationParameters validationParameters, BaseConfiguration configuration)
|
||
at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateSignatureAndIssuerSecurityKey(String token, JwtSecurityToken jwtToken, TokenValidationParameters validationParameters, BaseConfiguration configuration)
|
||
at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateJWS(String token, TokenValidationParameters validationParameters, BaseConfiguration currentConfiguration, SecurityToken& signatureValidatedToken, ExceptionDispatchInfo& exceptionThrown)
|
||
--- End of stack trace from previous location ---
|
||
at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateToken(String token, JwtSecurityToken outerToken, TokenValidationParameters validationParameters, SecurityToken& signatureValidatedToken)
|
||
at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateToken(String token, TokenValidationParameters validationParameters, SecurityToken& validatedToken)
|
||
at Microsoft.AspNetCore.Authentication.JwtBearer.JwtBearerHandler.HandleAuthenticateAsync()
|
||
2024-12-02 16:01:42.909 [INF] Bearer was not authenticated. Failure message: IDX10223: Lifetime validation failed. The token is expired. ValidTo (UTC): '08/10/2022 8:49:16 AM', Current time (UTC): '02/12/2024 10:31:42 AM'.
|
||
2024-12-02 16:01:42.911 [INF] Executing endpoint 'OnlineAssessment.V1.Controllers.UsersController.SignUpNew (API.User)'
|
||
2024-12-02 16:01:42.921 [INF] Route matched with {action = "SignUpNew", controller = "Users"}. Executing controller action with signature System.Threading.Tasks.Task`1[Microsoft.AspNetCore.Mvc.IActionResult] SignUpNew(OnlineAssessment.Domain.ViewModels.SignupRequestModel) on controller OnlineAssessment.V1.Controllers.UsersController (API.User).
|
||
2024-12-02 16:01:42.921 [DBG] Execution plan of authorization filters (in the following order): ["None"]
|
||
2024-12-02 16:01:42.921 [DBG] Execution plan of resource filters (in the following order): ["None"]
|
||
2024-12-02 16:01:42.922 [DBG] Execution plan of action filters (in the following order): ["Microsoft.AspNetCore.Mvc.ModelBinding.UnsupportedContentTypeFilter (Order: -3000)","Microsoft.AspNetCore.Mvc.Infrastructure.ModelStateInvalidFilter (Order: -2000)","Microsoft.AspNetCore.Mvc.ReportApiVersionsAttribute (Order: 0)"]
|
||
2024-12-02 16:01:42.922 [DBG] Execution plan of exception filters (in the following order): ["None"]
|
||
2024-12-02 16:01:42.922 [DBG] Execution plan of result filters (in the following order): ["Microsoft.AspNetCore.Mvc.Infrastructure.ClientErrorResultFilter (Order: -2000)","Microsoft.AspNetCore.Mvc.ReportApiVersionsAttribute (Order: 0)"]
|
||
2024-12-02 16:01:42.923 [DBG] Executing controller factory for controller OnlineAssessment.V1.Controllers.UsersController (API.User)
|
||
2024-12-02 16:01:43.107 [DBG] Executed controller factory for controller OnlineAssessment.V1.Controllers.UsersController (API.User)
|
||
2024-12-02 16:01:43.114 [DBG] Attempting to bind parameter 'request' of type 'OnlineAssessment.Domain.ViewModels.SignupRequestModel' ...
|
||
2024-12-02 16:01:43.115 [DBG] Attempting to bind parameter 'request' of type 'OnlineAssessment.Domain.ViewModels.SignupRequestModel' using the name '' in request data ...
|
||
2024-12-02 16:01:43.116 [DBG] Rejected input formatter 'Microsoft.AspNetCore.Mvc.Formatters.NewtonsoftJsonPatchInputFormatter' for content type 'application/json'.
|
||
2024-12-02 16:01:43.116 [DBG] Selected input formatter 'Microsoft.AspNetCore.Mvc.Formatters.NewtonsoftJsonInputFormatter' for content type 'application/json'.
|
||
2024-12-02 16:01:43.118 [DBG] Connection id "0HN8INI1KG6EC", Request id "0HN8INI1KG6EC:00000001": started reading request body.
|
||
2024-12-02 16:01:43.119 [DBG] Connection id "0HN8INI1KG6EC", Request id "0HN8INI1KG6EC:00000001": done reading request body.
|
||
2024-12-02 16:01:43.125 [DBG] Done attempting to bind parameter 'request' of type 'OnlineAssessment.Domain.ViewModels.SignupRequestModel'.
|
||
2024-12-02 16:01:43.125 [DBG] Done attempting to bind parameter 'request' of type 'OnlineAssessment.Domain.ViewModels.SignupRequestModel'.
|
||
2024-12-02 16:01:43.125 [DBG] Attempting to validate the bound parameter 'request' of type 'OnlineAssessment.Domain.ViewModels.SignupRequestModel' ...
|
||
2024-12-02 16:01:43.130 [DBG] Done attempting to validate the bound parameter 'request' of type 'OnlineAssessment.Domain.ViewModels.SignupRequestModel'.
|
||
2024-12-02 16:01:44.544 [DBG] No relationship from 'OrderPayment' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation', 'UpdatedByNavigation', 'User'} that could be matched with the properties on the other entity type - {'OrderPaymentCreatedByNavigation', 'OrderPaymentUpdatedByNavigation', 'OrderPaymentUser'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.550 [DBG] No relationship from 'Orders' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation', 'UpdatedByNavigation'} that could be matched with the properties on the other entity type - {'OrdersCreatedByNavigation', 'OrdersUpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.554 [DBG] No relationship from 'PracticeAttempts' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation', 'UpdatedByNavigation'} that could be matched with the properties on the other entity type - {'PracticeAttemptsCreatedByNavigation', 'PracticeAttemptsUpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.557 [DBG] No relationship from 'Practices' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation', 'UpdatedByNavigation'} that could be matched with the properties on the other entity type - {'PracticesCreatedByNavigation', 'PracticesUpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.559 [DBG] No relationship from 'QuestionBugs' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation', 'UpdatedByNavigation'} that could be matched with the properties on the other entity type - {'QuestionBugsCreatedByNavigation', 'QuestionBugsUpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.569 [DBG] No relationship from 'SubscribedExams' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation', 'UpdatedByNavigation'} that could be matched with the properties on the other entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.570 [DBG] No relationship from 'SubscribedPractices' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation', 'UpdatedByNavigation'} that could be matched with the properties on the other entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.581 [DBG] No relationship from 'Users' to 'OrderPayment' has been configured by convention because there are multiple properties on one entity type - {'OrderPaymentCreatedByNavigation', 'OrderPaymentUpdatedByNavigation', 'OrderPaymentUser'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation', 'User'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.581 [DBG] No relationship from 'Users' to 'Orders' has been configured by convention because there are multiple properties on one entity type - {'OrdersCreatedByNavigation', 'OrdersUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.581 [DBG] No relationship from 'Users' to 'PracticeAttempts' has been configured by convention because there are multiple properties on one entity type - {'PracticeAttemptsCreatedByNavigation', 'PracticeAttemptsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.581 [DBG] No relationship from 'Users' to 'Practices' has been configured by convention because there are multiple properties on one entity type - {'PracticesCreatedByNavigation', 'PracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.581 [DBG] No relationship from 'Users' to 'QuestionBugs' has been configured by convention because there are multiple properties on one entity type - {'QuestionBugsCreatedByNavigation', 'QuestionBugsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.581 [DBG] No relationship from 'Users' to 'SubscribedExams' has been configured by convention because there are multiple properties on one entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.581 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.867 [DBG] No relationship from 'OrderPayment' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation', 'UpdatedByNavigation', 'User'} that could be matched with the properties on the other entity type - {'OrderPaymentCreatedByNavigation', 'OrderPaymentUpdatedByNavigation', 'OrderPaymentUser'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.868 [DBG] No relationship from 'Users' to 'OrderPayment' has been configured by convention because there are multiple properties on one entity type - {'OrderPaymentCreatedByNavigation', 'OrderPaymentUpdatedByNavigation', 'OrderPaymentUser'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation', 'User'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.868 [DBG] No relationship from 'Users' to 'Orders' has been configured by convention because there are multiple properties on one entity type - {'OrdersCreatedByNavigation', 'OrdersUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.868 [DBG] No relationship from 'Users' to 'PracticeAttempts' has been configured by convention because there are multiple properties on one entity type - {'PracticeAttemptsCreatedByNavigation', 'PracticeAttemptsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.868 [DBG] No relationship from 'Users' to 'Practices' has been configured by convention because there are multiple properties on one entity type - {'PracticesCreatedByNavigation', 'PracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.868 [DBG] No relationship from 'Users' to 'QuestionBugs' has been configured by convention because there are multiple properties on one entity type - {'QuestionBugsCreatedByNavigation', 'QuestionBugsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.868 [DBG] No relationship from 'Users' to 'SubscribedExams' has been configured by convention because there are multiple properties on one entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.868 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.870 [DBG] No relationship from 'Users' to 'OrderPayment' has been configured by convention because there are multiple properties on one entity type - {'OrderPaymentUpdatedByNavigation', 'OrderPaymentUser'} that could be matched with the properties on the other entity type - {'UpdatedByNavigation', 'User'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.870 [DBG] No relationship from 'Users' to 'Orders' has been configured by convention because there are multiple properties on one entity type - {'OrdersCreatedByNavigation', 'OrdersUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.870 [DBG] No relationship from 'Users' to 'PracticeAttempts' has been configured by convention because there are multiple properties on one entity type - {'PracticeAttemptsCreatedByNavigation', 'PracticeAttemptsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.870 [DBG] No relationship from 'Users' to 'Practices' has been configured by convention because there are multiple properties on one entity type - {'PracticesCreatedByNavigation', 'PracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.870 [DBG] No relationship from 'Users' to 'QuestionBugs' has been configured by convention because there are multiple properties on one entity type - {'QuestionBugsCreatedByNavigation', 'QuestionBugsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.870 [DBG] No relationship from 'Users' to 'SubscribedExams' has been configured by convention because there are multiple properties on one entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.870 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.870 [DBG] No relationship from 'OrderPayment' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation'} that could be matched with the properties on the other entity type - {'OrderPaymentCreatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.870 [DBG] No relationship from 'OrderPayment' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'UpdatedByNavigation', 'User'} that could be matched with the properties on the other entity type - {'OrderPaymentUpdatedByNavigation', 'OrderPaymentUser'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.873 [DBG] No relationship from 'OrderPayment' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'UpdatedByNavigation', 'User'} that could be matched with the properties on the other entity type - {'OrderPaymentUpdatedByNavigation', 'OrderPaymentUser'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.874 [DBG] No relationship from 'Users' to 'OrderPayment' has been configured by convention because there are multiple properties on one entity type - {'OrderPaymentCreatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.874 [DBG] No relationship from 'Users' to 'OrderPayment' has been configured by convention because there are multiple properties on one entity type - {'OrderPaymentUpdatedByNavigation', 'OrderPaymentUser'} that could be matched with the properties on the other entity type - {'UpdatedByNavigation', 'User'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.874 [DBG] No relationship from 'Users' to 'Orders' has been configured by convention because there are multiple properties on one entity type - {'OrdersCreatedByNavigation', 'OrdersUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.874 [DBG] No relationship from 'Users' to 'PracticeAttempts' has been configured by convention because there are multiple properties on one entity type - {'PracticeAttemptsCreatedByNavigation', 'PracticeAttemptsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.874 [DBG] No relationship from 'Users' to 'Practices' has been configured by convention because there are multiple properties on one entity type - {'PracticesCreatedByNavigation', 'PracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.874 [DBG] No relationship from 'Users' to 'QuestionBugs' has been configured by convention because there are multiple properties on one entity type - {'QuestionBugsCreatedByNavigation', 'QuestionBugsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.874 [DBG] No relationship from 'Users' to 'SubscribedExams' has been configured by convention because there are multiple properties on one entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.874 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.875 [DBG] No relationship from 'Users' to 'Orders' has been configured by convention because there are multiple properties on one entity type - {'OrdersCreatedByNavigation', 'OrdersUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.876 [DBG] No relationship from 'Users' to 'PracticeAttempts' has been configured by convention because there are multiple properties on one entity type - {'PracticeAttemptsCreatedByNavigation', 'PracticeAttemptsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.876 [DBG] No relationship from 'Users' to 'Practices' has been configured by convention because there are multiple properties on one entity type - {'PracticesCreatedByNavigation', 'PracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.876 [DBG] No relationship from 'Users' to 'QuestionBugs' has been configured by convention because there are multiple properties on one entity type - {'QuestionBugsCreatedByNavigation', 'QuestionBugsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.876 [DBG] No relationship from 'Users' to 'SubscribedExams' has been configured by convention because there are multiple properties on one entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.876 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.881 [DBG] No relationship from 'Orders' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation', 'UpdatedByNavigation'} that could be matched with the properties on the other entity type - {'OrdersCreatedByNavigation', 'OrdersUpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.882 [DBG] No relationship from 'Users' to 'Orders' has been configured by convention because there are multiple properties on one entity type - {'OrdersCreatedByNavigation', 'OrdersUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.882 [DBG] No relationship from 'Users' to 'PracticeAttempts' has been configured by convention because there are multiple properties on one entity type - {'PracticeAttemptsCreatedByNavigation', 'PracticeAttemptsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.882 [DBG] No relationship from 'Users' to 'Practices' has been configured by convention because there are multiple properties on one entity type - {'PracticesCreatedByNavigation', 'PracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.882 [DBG] No relationship from 'Users' to 'QuestionBugs' has been configured by convention because there are multiple properties on one entity type - {'QuestionBugsCreatedByNavigation', 'QuestionBugsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.882 [DBG] No relationship from 'Users' to 'SubscribedExams' has been configured by convention because there are multiple properties on one entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.882 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.884 [DBG] No relationship from 'Users' to 'PracticeAttempts' has been configured by convention because there are multiple properties on one entity type - {'PracticeAttemptsCreatedByNavigation', 'PracticeAttemptsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.884 [DBG] No relationship from 'Users' to 'Practices' has been configured by convention because there are multiple properties on one entity type - {'PracticesCreatedByNavigation', 'PracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.884 [DBG] No relationship from 'Users' to 'QuestionBugs' has been configured by convention because there are multiple properties on one entity type - {'QuestionBugsCreatedByNavigation', 'QuestionBugsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.884 [DBG] No relationship from 'Users' to 'SubscribedExams' has been configured by convention because there are multiple properties on one entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.884 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.895 [DBG] No relationship from 'PracticeAttempts' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation', 'UpdatedByNavigation'} that could be matched with the properties on the other entity type - {'PracticeAttemptsCreatedByNavigation', 'PracticeAttemptsUpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.896 [DBG] No relationship from 'Users' to 'PracticeAttempts' has been configured by convention because there are multiple properties on one entity type - {'PracticeAttemptsCreatedByNavigation', 'PracticeAttemptsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.896 [DBG] No relationship from 'Users' to 'Practices' has been configured by convention because there are multiple properties on one entity type - {'PracticesCreatedByNavigation', 'PracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.896 [DBG] No relationship from 'Users' to 'QuestionBugs' has been configured by convention because there are multiple properties on one entity type - {'QuestionBugsCreatedByNavigation', 'QuestionBugsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.896 [DBG] No relationship from 'Users' to 'SubscribedExams' has been configured by convention because there are multiple properties on one entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.896 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.898 [DBG] No relationship from 'Users' to 'Practices' has been configured by convention because there are multiple properties on one entity type - {'PracticesCreatedByNavigation', 'PracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.898 [DBG] No relationship from 'Users' to 'QuestionBugs' has been configured by convention because there are multiple properties on one entity type - {'QuestionBugsCreatedByNavigation', 'QuestionBugsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.898 [DBG] No relationship from 'Users' to 'SubscribedExams' has been configured by convention because there are multiple properties on one entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.898 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.907 [DBG] No relationship from 'Practices' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation', 'UpdatedByNavigation'} that could be matched with the properties on the other entity type - {'PracticesCreatedByNavigation', 'PracticesUpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.908 [DBG] No relationship from 'Users' to 'Practices' has been configured by convention because there are multiple properties on one entity type - {'PracticesCreatedByNavigation', 'PracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.908 [DBG] No relationship from 'Users' to 'QuestionBugs' has been configured by convention because there are multiple properties on one entity type - {'QuestionBugsCreatedByNavigation', 'QuestionBugsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.908 [DBG] No relationship from 'Users' to 'SubscribedExams' has been configured by convention because there are multiple properties on one entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.908 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.910 [DBG] No relationship from 'Users' to 'QuestionBugs' has been configured by convention because there are multiple properties on one entity type - {'QuestionBugsCreatedByNavigation', 'QuestionBugsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.910 [DBG] No relationship from 'Users' to 'SubscribedExams' has been configured by convention because there are multiple properties on one entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.910 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.917 [DBG] No relationship from 'QuestionBugs' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation', 'UpdatedByNavigation'} that could be matched with the properties on the other entity type - {'QuestionBugsCreatedByNavigation', 'QuestionBugsUpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.917 [DBG] No relationship from 'Users' to 'QuestionBugs' has been configured by convention because there are multiple properties on one entity type - {'QuestionBugsCreatedByNavigation', 'QuestionBugsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.917 [DBG] No relationship from 'Users' to 'SubscribedExams' has been configured by convention because there are multiple properties on one entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.918 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.919 [DBG] No relationship from 'Users' to 'SubscribedExams' has been configured by convention because there are multiple properties on one entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.919 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.946 [DBG] No relationship from 'SubscribedExams' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation', 'UpdatedByNavigation'} that could be matched with the properties on the other entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.946 [DBG] No relationship from 'Users' to 'SubscribedExams' has been configured by convention because there are multiple properties on one entity type - {'SubscribedExamsCreatedByNavigation', 'SubscribedExamsUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.947 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.948 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.953 [DBG] No relationship from 'SubscribedPractices' to 'Users' has been configured by convention because there are multiple properties on one entity type - {'CreatedByNavigation', 'UpdatedByNavigation'} that could be matched with the properties on the other entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:44.954 [DBG] No relationship from 'Users' to 'SubscribedPractices' has been configured by convention because there are multiple properties on one entity type - {'SubscribedPracticesCreatedByNavigation', 'SubscribedPracticesUpdatedByNavigation'} that could be matched with the properties on the other entity type - {'CreatedByNavigation', 'UpdatedByNavigation'}. This message can be disregarded if explicit configuration has been specified in 'OnModelCreating'.
|
||
2024-12-02 16:01:45.003 [DBG] The index {'SubjectId'} was not created on entity type 'Categories' as the properties are already covered by the index {'SubjectId', 'Name', 'IsActive'}.
|
||
2024-12-02 16:01:45.003 [DBG] The index {'InstituteId'} was not created on entity type 'Classes' as the properties are already covered by the index {'InstituteId', 'Name', 'IsActive'}.
|
||
2024-12-02 16:01:45.003 [DBG] The index {'ExamId'} was not created on entity type 'ExamSections' as the properties are already covered by the index {'ExamId', 'SubjectId', 'IsActive'}.
|
||
2024-12-02 16:01:45.003 [DBG] The index {'QuestionId'} was not created on entity type 'QuestionCategories' as the properties are already covered by the index {'QuestionId', 'CategoryId', 'IsActive'}.
|
||
2024-12-02 16:01:45.003 [DBG] The index {'QuestionId'} was not created on entity type 'QuestionLanguges' as the properties are already covered by the index {'QuestionId', 'LanguageId', 'IsActive'}.
|
||
2024-12-02 16:01:45.003 [DBG] The index {'QuestionOptionId'} was not created on entity type 'QuestionOptionLanguages' as the properties are already covered by the index {'QuestionOptionId', 'LanguageId', 'IsActive'}.
|
||
2024-12-02 16:01:45.003 [DBG] The index {'QuestionId'} was not created on entity type 'QuestionTags' as the properties are already covered by the index {'QuestionId', 'TagId', 'IsActive'}.
|
||
2024-12-02 16:01:45.003 [DBG] The index {'ClassId'} was not created on entity type 'Subjects' as the properties are already covered by the index {'ClassId', 'Name', 'IsActive'}.
|
||
2024-12-02 16:01:45.003 [DBG] The index {'UserGroupId'} was not created on entity type 'UserGroupMembers' as the properties are already covered by the index {'UserGroupId', 'UserId', 'IsActive'}.
|
||
2024-12-02 16:01:45.003 [DBG] The index {'ClassId'} was not created on entity type 'UserGroups' as the properties are already covered by the index {'ClassId', 'Name', 'IsActive'}.
|
||
2024-12-02 16:01:45.003 [DBG] The index {'InstituteId'} was not created on entity type 'Users' as the properties are already covered by the index {'InstituteId', 'EmailId'}.
|
||
2024-12-02 16:01:45.249 [DBG] Entity Framework Core 9.0.0 initialized 'OnlineAssessmentContext' using provider 'Microsoft.EntityFrameworkCore.SqlServer:9.0.0' with options: MaxPoolSize=1024 EngineType=SqlServer
|
||
2024-12-02 16:01:45.254 [DBG] Creating DbConnection.
|
||
2024-12-02 16:01:45.277 [DBG] Created DbConnection. (22ms).
|
||
2024-12-02 16:01:45.278 [DBG] Opening connection to database 'odiproj1_oa' on server '68.71.130.74,1533'.
|
||
2024-12-02 16:01:46.998 [DBG] Opened connection to database 'odiproj1_oa' on server '68.71.130.74,1533'.
|
||
2024-12-02 16:01:47.000 [DBG] Beginning transaction with isolation level 'Unspecified'.
|
||
2024-12-02 16:01:47.270 [DBG] Began transaction with isolation level 'ReadCommitted'.
|
||
2024-12-02 16:01:47.303 [DBG] 'OnlineAssessmentContext' generated a temporary value for the property 'Users.Id'. Consider using 'DbContextOptionsBuilder.EnableSensitiveDataLogging' to see key values.
|
||
2024-12-02 16:01:47.384 [DBG] Context 'OnlineAssessmentContext' started tracking 'Users' entity. Consider using 'DbContextOptionsBuilder.EnableSensitiveDataLogging' to see key values.
|
||
2024-12-02 16:01:47.386 [DBG] SaveChanges starting for 'OnlineAssessmentContext'.
|
||
2024-12-02 16:01:47.388 [DBG] DetectChanges starting for 'OnlineAssessmentContext'.
|
||
2024-12-02 16:01:47.398 [DBG] DetectChanges completed for 'OnlineAssessmentContext'.
|
||
2024-12-02 16:01:47.485 [DBG] Creating transaction savepoint.
|
||
2024-12-02 16:01:47.756 [DBG] Created transaction savepoint.
|
||
2024-12-02 16:01:47.759 [DBG] Creating DbCommand for 'ExecuteReader'.
|
||
2024-12-02 16:01:47.761 [DBG] Created DbCommand for 'ExecuteReader' (0ms).
|
||
2024-12-02 16:01:47.766 [DBG] Initialized DbCommand for 'ExecuteReader' (7ms).
|
||
2024-12-02 16:01:47.771 [DBG] Executing DbCommand [Parameters=[@p0='?' (Size = 100), @p1='?' (Size = 1500) (DbType = AnsiString), @p2='?' (DbType = Int32), @p3='?' (Size = 1500) (DbType = AnsiString), @p4='?' (Size = 1500) (DbType = AnsiString), @p5='?' (DbType = Int32), @p6='?' (DbType = DateTime), @p7='?' (DbType = Date), @p8='?' (Size = 500) (DbType = AnsiString), @p9='?' (Size = 50), @p10='?' (Size = 10) (DbType = AnsiString), @p11='?' (DbType = Int32), @p12='?' (DbType = Boolean), @p13='?' (DbType = Int32), @p14='?' (Size = 50) (DbType = AnsiString), @p15='?' (Size = 20) (DbType = AnsiString), @p16='?' (Size = 20) (DbType = AnsiString), @p17='?' (Size = 10) (DbType = AnsiString), @p18='?' (Size = 1000) (DbType = AnsiString), @p19='?' (Size = 6) (DbType = AnsiString), @p20='?' (DbType = DateTime), @p21='?' (DbType = Int32), @p22='?' (DbType = Int32), @p23='?' (Size = 50) (DbType = AnsiString), @p24='?' (DbType = Int32), @p25='?' (DbType = DateTime), @p26='?' (Size = 500), @p27='?' (Size = 10) (DbType = AnsiString), @p28='?' (Size = 512)], CommandType='"Text"', CommandTimeout='30']
|
||
SET IMPLICIT_TRANSACTIONS OFF;
|
||
SET NOCOUNT ON;
|
||
INSERT INTO [dbo].[Users] ([access_token], [address], [batch_id], [city], [country], [created_by], [created_on], [date_of_birth], [email_id], [first_name], [gender], [institute_id], [is_active], [language_id], [last_name], [latitude], [longitude], [mobile_no], [photo], [pin_code], [registration_datetime], [registration_id], [role_id], [state_code], [updated_by], [updated_on], [user_password], [user_salt], [uuid])
|
||
OUTPUT INSERTED.[id]
|
||
VALUES (@p0, @p1, @p2, @p3, @p4, @p5, @p6, @p7, @p8, @p9, @p10, @p11, @p12, @p13, @p14, @p15, @p16, @p17, @p18, @p19, @p20, @p21, @p22, @p23, @p24, @p25, @p26, @p27, @p28);
|
||
2024-12-02 16:01:48.062 [INF] Executed DbCommand (286ms) [Parameters=[@p0='?' (Size = 100), @p1='?' (Size = 1500) (DbType = AnsiString), @p2='?' (DbType = Int32), @p3='?' (Size = 1500) (DbType = AnsiString), @p4='?' (Size = 1500) (DbType = AnsiString), @p5='?' (DbType = Int32), @p6='?' (DbType = DateTime), @p7='?' (DbType = Date), @p8='?' (Size = 500) (DbType = AnsiString), @p9='?' (Size = 50), @p10='?' (Size = 10) (DbType = AnsiString), @p11='?' (DbType = Int32), @p12='?' (DbType = Boolean), @p13='?' (DbType = Int32), @p14='?' (Size = 50) (DbType = AnsiString), @p15='?' (Size = 20) (DbType = AnsiString), @p16='?' (Size = 20) (DbType = AnsiString), @p17='?' (Size = 10) (DbType = AnsiString), @p18='?' (Size = 1000) (DbType = AnsiString), @p19='?' (Size = 6) (DbType = AnsiString), @p20='?' (DbType = DateTime), @p21='?' (DbType = Int32), @p22='?' (DbType = Int32), @p23='?' (Size = 50) (DbType = AnsiString), @p24='?' (DbType = Int32), @p25='?' (DbType = DateTime), @p26='?' (Size = 500), @p27='?' (Size = 10) (DbType = AnsiString), @p28='?' (Size = 512)], CommandType='"Text"', CommandTimeout='30']
|
||
SET IMPLICIT_TRANSACTIONS OFF;
|
||
SET NOCOUNT ON;
|
||
INSERT INTO [dbo].[Users] ([access_token], [address], [batch_id], [city], [country], [created_by], [created_on], [date_of_birth], [email_id], [first_name], [gender], [institute_id], [is_active], [language_id], [last_name], [latitude], [longitude], [mobile_no], [photo], [pin_code], [registration_datetime], [registration_id], [role_id], [state_code], [updated_by], [updated_on], [user_password], [user_salt], [uuid])
|
||
OUTPUT INSERTED.[id]
|
||
VALUES (@p0, @p1, @p2, @p3, @p4, @p5, @p6, @p7, @p8, @p9, @p10, @p11, @p12, @p13, @p14, @p15, @p16, @p17, @p18, @p19, @p20, @p21, @p22, @p23, @p24, @p25, @p26, @p27, @p28);
|
||
2024-12-02 16:01:48.073 [DBG] The foreign key property 'Users.Id' was detected as changed. Consider using 'DbContextOptionsBuilder.EnableSensitiveDataLogging' to see property values.
|
||
2024-12-02 16:01:48.079 [DBG] Closing data reader to 'odiproj1_oa' on server '68.71.130.74,1533'.
|
||
2024-12-02 16:01:48.082 [DBG] A data reader for 'odiproj1_oa' on server '68.71.130.74,1533' is being disposed after spending 17ms reading results.
|
||
2024-12-02 16:01:48.088 [DBG] An entity of type 'Users' tracked by 'OnlineAssessmentContext' changed state from '"Added"' to '"Unchanged"'. Consider using 'DbContextOptionsBuilder.EnableSensitiveDataLogging' to see key values.
|
||
2024-12-02 16:01:48.088 [DBG] SaveChanges completed for 'OnlineAssessmentContext' with 1 entities written to the database.
|
||
2024-12-02 16:01:48.089 [DBG] Committing transaction.
|
||
2024-12-02 16:01:48.354 [DBG] Committed transaction.
|
||
2024-12-02 16:01:48.355 [DBG] Closing connection to database 'odiproj1_oa' on server '68.71.130.74,1533'.
|
||
2024-12-02 16:01:48.359 [DBG] Closed connection to database 'odiproj1_oa' on server '68.71.130.74,1533' (3ms).
|
||
2024-12-02 16:02:34.886 [DBG] List of registered output formatters, in the following order: ["Microsoft.AspNetCore.Mvc.Formatters.HttpNoContentOutputFormatter","Microsoft.AspNetCore.Mvc.Formatters.StringOutputFormatter","Microsoft.AspNetCore.Mvc.Formatters.StreamOutputFormatter","Microsoft.AspNetCore.Mvc.Formatters.NewtonsoftJsonOutputFormatter"]
|
||
2024-12-02 16:02:34.890 [DBG] No information found on request to perform content negotiation.
|
||
2024-12-02 16:02:34.890 [DBG] Attempting to select an output formatter without using a content type as no explicit content types were specified for the response.
|
||
2024-12-02 16:02:34.890 [DBG] Attempting to select the first formatter in the output formatters list which can write the result.
|
||
2024-12-02 16:02:34.897 [DBG] Selected output formatter 'Microsoft.AspNetCore.Mvc.Formatters.NewtonsoftJsonOutputFormatter' and content type 'application/json' to write the response.
|
||
2024-12-02 16:02:34.897 [INF] Executing OkObjectResult, writing value of type 'OnlineAssessment.Common.ReturnResponse'.
|
||
2024-12-02 16:02:34.914 [INF] Executed action OnlineAssessment.V1.Controllers.UsersController.SignUpNew (API.User) in 51989.494ms
|
||
2024-12-02 16:02:34.917 [INF] Executed endpoint 'OnlineAssessment.V1.Controllers.UsersController.SignUpNew (API.User)'
|
||
2024-12-02 16:02:34.919 [INF] HTTP POST /v1/Users/SignUpNew responded 200 in 52663.5671 ms
|
||
2024-12-02 16:02:34.921 [DBG] Connection id "0HN8INI1KG6EC" completed keep alive response.
|
||
2024-12-02 16:02:34.940 [INF] Request finished HTTP/1.1 POST http://localhost:8008/v1/Users/SignUpNew - 200 249 application/json; charset=utf-8 52687.9303ms
|