Hey, I've been running into issues trying to figure out how a user could be
able to access multiple versions of an app. Here is the following example:
I have an app named ANNA. ANNA is used to build labels and these labels
are dependent upon different standards that come out. For example, we have
standard 1700, standard 1800, standard 1900. The DjangoProject website has
a bottom corner button that allows you to go to different versions of the
django docs. I would like to implement that into ANNA, however I've come
across a number of problems. So ANNA has the following app structure:
my_project
- ANNA
- build (development)
- search (development)
I have tried to implement this versioning by the following partition
*PARTITION 1*
my_project
- ANNA
- build (development)
- search (development)
- build1700
- search1700
- build1800
- search1800
- build1900
- search1900
Unfortunately, the models used in all versions of build are the same across
the board, and Django's reverse lookup for these models is giving me
issues. For instance if I have a label model in build, I will also have a
label model in build1700, build1800, etc. So I have to change the model
names for each version, which means I have to change all of the business
code to be version specific -- and I really do not want to do that since
our label standards are also in development and change quite rapidly (like
every four months right now). The versions are also similar enough to
where when a new one comes out, I would like to be able to pretty much copy
and paste the last version's code into the new version's code and make my
changes like so.
Has anyone ever had to do anything like this or have any ideas of how to go
about it?
Also, below is my current callback.
Unhandled exception in thread started by <function wrapper at 0x38639b0>
> Traceback (most recent call last):
> File "/usr/lib64/python2.7/site-packages/django/utils/autoreload.py",
> line 227, in wrapper
> fn(*args, **kwargs)
> File
> "/usr/lib64/python2.7/site-packages/django/core/management/commands/runserver.py",
>
> line 125, in inner_run
> self.check(display_num_errors=True)
> File
> "/usr/lib64/python2.7/site-packages/django/core/management/base.py", line
> 405, in check
> raise SystemCheckError(msg)
> django.core.management.base.SystemCheckError: SystemCheckError: System
> check identified some issues:
>
> ERRORS:
> build1700.Bundle.user: (fields.E304) Reverse accessor for 'Bundle.user'
> clashes with reverse accessor for 'Bundle.user'.
> HINT: Add or change a related_name argument to the definition for
> 'Bundle.user' or 'Bundle.user'.
> build.Bundle.user: (fields.E304) Reverse accessor for 'Bundle.user'
> clashes with reverse accessor for 'Bundle.user'.
> HINT: Add or change a related_name argument to the definition for
> 'Bundle.user' or 'Bundle.user'.
>
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/4ae70d15-12a3-44bd-9dfe-7666eab9e658%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
