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
AssertionError: The schema for the "reahl-web-declarative" egg has already been created previously at version 4.0.2 #141
Comments
The easy way to fix this is to use a different database for each application... Now to figure out how to configure what database reahl uses... |
I could not figure out how to configure what database reahl uses... so I used |
It would be the best to drop it, as reahl needs its own tables per application. The error you got when creating the tables for you second application is caused by the createdbtables wanting to create the reahl required tables again, as the default database is the same for both of you applications. To see which config you have, assuming you have an etc directory like in the examples:
you should note that the output of the command would provide you with a hint(I'm running linux):
To create a different database for your application, you need to create a config file to specifiy it. Create or edit a file in the etc directory called reahl.config.py. Add the follwing to it, or whatever will work for your windows machine:
Remember to run:
More database connection examples can be found here:
|
The thing that is perhaps confusing here is that we print a stacktrace. We do this a lot. A better interface would be to always catch errors we know can happen and report them to the user in words a user can understand... so that stacktrace would mean "there's something seriously broken" instead. We have built a bit of infrastructure to do this reporting better. If you thrown a DomainException instead of an arbitrary one. See: https://github.com/reahl/reahl/blob/master/reahl-component/reahl/component/shelltools.py#L204 Perhaps we can create a few "beginner" tasks for handing such exceptions better by throwing DomainExceptions with more useful messages |
The following statement:
"""
WARNING:reahl.component.config:reahlsystem.connection_uri in etc/
reahl.config.py is using a dangerous default setting:
sqlite:////tmp/reahl.db
"""
is only correct if there were a file named reahl.config.py in the etc
directory of my project, which there is not. To be fully correct, "etc/
reahl.config.py" is a relative path, so perhaps there is a default etc
directory outside of my project with a reahl.config.py file. But there
certainly is not one in my project.
…On Sun, Oct 21, 2018 at 12:34 AM Iwan Vosloo ***@***.***> wrote:
The thing that is perhaps confusing here is that we print a stacktrace. We
do this a lot.
A better interface would be to always catch errors we know can happen and
report them to the user in words a user can understand... so that
stacktrace would mean "there's something seriously broken" instead.
We have built a bit of infrastructure to do this reporting better. If you
thrown a DomainException instead of an arbitrary one. See:
https://github.com/reahl/reahl/blob/master/reahl-component/reahl/component/shelltools.py#L204
Perhaps we can create a few "beginner" tasks for handing such exceptions
better by throwing DomainExceptions with more useful messages
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#141 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AABTLVKOKoUn6JKSgMufeHbJL75H_bufks5unBV-gaJpZM4XxX8r>
.
|
I hear you. We can word it differently, thanks! |
When attempting to run the addressbook1 example, I get the following error transcript:
The text was updated successfully, but these errors were encountered: