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

removing Crane #146

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

removing Crane #146

wants to merge 1 commit into from

Conversation

vindarel
Copy link
Collaborator

I'd love to love Crane but it has too many open issues and the author
is busy elsewhere. I couldn't even connect to a DB. Migrations do not
work with sqlite. Users reported errors, they are not versioned.

Mito worked out of the box for me.

I'd love to love Crane but it has too many open issues and the author
is busy elsewhere. I couldn't even connect to a DB. Migrations do not
work with sqlite. Users reported errors, they are not versioned.

Mito worked out of the box for me.
@rudolfochrist
Copy link
Contributor

But beware, that mito is still very alpha (as advertised by the author). I made the mistake to chose it for a web shop/marketplace platform last year and it was more hassle than benefit.

@vindarel
Copy link
Collaborator Author

vindarel commented Jan 19, 2018

damn, really ? ok I won't push it then. It seems ok to me so far (*cough* many-to-many relationships). What do you recommend instead ? (to register objects to a db, define relationships, have (versioned) migrations,… ?)

(edit) and what task turned a hassle ?

@rudolfochrist
Copy link
Contributor

Disclaimer: I'm not really good in remembering those things. I usually keep that it was troublesome and forget about the details. Anyway.

Memory consumption went up after running the application for a longer period of time, connection management made us some troubles, it was somewhat slow and when an error occurred we had to debug 10+ fukamachi libraries.

I don't have anything special to recommend. I'm now in the write-queries-by-hand camp and doing migrations manually.

I'm unsure about crane. Perhaps it is abandoned and then it should be removed from the list. Nonetheless I think we still should keep mito, but don't promote it as the go to option.

1 similar comment
@rudolfochrist
Copy link
Contributor

Disclaimer: I'm not really good in remembering those things. I usually keep that it was troublesome and forget about the details. Anyway.

Memory consumption went up after running the application for a longer period of time, connection management made us some troubles, it was somewhat slow and when an error occurred we had to debug 10+ fukamachi libraries.

I don't have anything special to recommend. I'm now in the write-queries-by-hand camp and doing migrations manually.

I'm unsure about crane. Perhaps it is abandoned and then it should be removed from the list. Nonetheless I think we still should keep mito, but don't promote it as the go to option.

@vindarel
Copy link
Collaborator Author

agreed, I'll leave this open a bit in case someone else has more feedback, and I won't merge this PR.

Thanks for the feedback.

@cage2
Copy link
Contributor

cage2 commented Sep 25, 2018

Hello!

FWIW i keep a patched repository of crane that works with sqlite3 (limited migration is supported too).

Any help is appreciated! :)
Bye!
C.

@vindarel
Copy link
Collaborator Author

Hi @cage2, I only see a log4cl fork in your repositories, where's Crane ? thanks

@cage2
Copy link
Contributor

cage2 commented Sep 26, 2018 via email

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

Successfully merging this pull request may close these issues.

3 participants