derek wrote:
>
>>> On the other hand, if the two websites are entirely independent, putting
>>> them into a single database is simply poor design. It's trivial to
>>> create a separate database and why not use the tools that are available
>>> instead of adding extra complexity?!
>> I think the
> > On the other hand, if the two websites are entirely independent, putting
> > them into a single database is simply poor design. It's trivial to
> > create a separate database and why not use the tools that are available
> > instead of adding extra complexity?!
>
> I think the idea is to
Malcolm Tredinnick wrote:
> On Wed, 2009-08-05 at 17:59 +0100, Robin Becker wrote:
>> My boss wants to have two different django controlled websites with a common
>> database. Is there a way to do this?
>>
>> We are already running multiple websites into a single django project and
>> because
On Wed, 2009-08-05 at 17:59 +0100, Robin Becker wrote:
> My boss wants to have two different django controlled websites with a common
> database. Is there a way to do this?
>
> We are already running multiple websites into a single django project and
> because they have a disambiguating term
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There is no problem with that, as long as your code accounts for it.
Luke
luke.seelenbin...@gmail.com
Robin Becker wrote:
> My boss wants to have two different django controlled websites with a common
> database. Is there a way to do this?
>
>
My boss wants to have two different django controlled websites with a common
database. Is there a way to do this?
We are already running multiple websites into a single django project and
because they have a disambiguating term in the urls eg each url has
/lang/brand/path we can map the
6 matches
Mail list logo
