Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with migration (Postgresql) #1109

Open
Alexander-Zender opened this issue Apr 8, 2024 · 8 comments
Open

Issue with migration (Postgresql) #1109

Alexander-Zender opened this issue Apr 8, 2024 · 8 comments

Comments

@Alexander-Zender
Copy link

First of, great work on the new release @enkodellc !

I was setting up a new project with the new release using postgresql, when I encountered an issue.
When creating the migration, I encountered this error:
image

I could pinpoint it to the Company and Person model. They use a Point object for the Location property.
When commenting it out or adding the [NotMapped] annotation, the migration works.

I do not know if this is a postgresql only issue.

@Alexander-Zender
Copy link
Author

Alexander-Zender commented Apr 8, 2024

Additionally, the datetime2 data type used for the AuditTrail, as well as nvarchar used when using the MaxLengh Annotation are not supported too
one can manually change it all but that might not be the best approach

Additionally something was changed to ngpsql in version 6 with the datetime:
https://www.npgsql.org/doc/release-notes/6.0.html#major-changes-to-timestamp-mapping

I was able to generate the database but not yet add any entities with datetime fields

@enkodellc
Copy link
Owner

@Alexander-Zender do you want to submit a PR? Since you are using Postgres and I do not have it on my system it would be best for you do that and contribute. Thanks

@Alexander-Zender
Copy link
Author

Alexander-Zender commented Apr 9, 2024

@enkodellc Yes, Im preparing one.
I encountered that the login is broken, with some metadata can not be found.

image

This error is also in the demo version, as well as some pages are simply broken (paging or virtual table).

image

The current release seem to not be stable.

Update:

The error seem to be that the baseapiclient can not process/receive(?) the metadata from the breeze controller.
image

When it is initialized, the applicationcontroller metadata function is called however and returns the metadata. However, the BaseApiClient never receives it.
I tested the metadata API call manually and a valid json is returned. The issue is somewhere in the middleware(?)

@Alexander-Zender
Copy link
Author

@enkodellc Postgresql support PR open, as far as I can see it works with MS SQL and Postgresql just requires a new migration creation for each.

There might be a dirty fix in the startup file. However, I did not know how to else access the variable.
Maybe you have more expertise for this

@Alexander-Zender
Copy link
Author

@enkodellc Could you check out the breeze problems I have mentioned above?

@enkodellc
Copy link
Owner

enkodellc commented Apr 12, 2024

Sorry I am going on Vacation and have been busy. @GioviQ do you have a minute to review. If not I will have to check when I get back. Thanks. I merged all the changes in a Postgres Branch.

@GioviQ
Copy link
Collaborator

GioviQ commented Apr 12, 2024

It seems there are features partially copied from Maui branch like Person entities. I deleted Person, but then other pages have troubles.

@AlexanderZender
Copy link

@enkodellc Any updates on the last release issues?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants