It's possible but you may need to split out django and non-django into a
front and back end. This sounds similar to phpmyadmin or phppgadmin
I think the key to this is that django only be used to store the user
and connection information for each database (And provide a web
interface). When a
Am Dienstag, 16. April 2013 17:52:11 UTC+2 schrieb אברהם סרור:
>
> So you are saying that each user models will be using the same database
> but with different connection settings?
>
Yes, exactly. Each user has his own username. That's what the SQL command
"create user xy" is for exactly. I do
So you are saying that each user models will be using the same database but
with different connection settings?
I believe you can create each and every connection setting on your
databases inside settings.py, each one would use the same database but a
different user.
When creating an object specif
I looked at that a bit, thanks, the problem is that I can well use my pg
server to do the authentication, but I still can't talk django into using
the database connection for this particurlar user (hopefully I'm just not
aware of the solution).
You see, lots of my models in models.py are based
I believe you could create a custom auth that relies on the postgres auth
system
On Tue, Apr 16, 2013 at 3:00 PM, Maximilian Tyrtania <
maximilian.tyrta...@googlemail.com> wrote:
> Hi there,
>
> This is my 1st post, so please be gentle...
>
> I'm looking into using django as web front end to my
Hi there,
This is my 1st post, so please be gentle...
I'm looking into using django as web front end to my Postgres DB. Now in my
PG server i have a number of db users (created via create user xy...), and
I would like to use these users as well in my django->postgres connections.
Obviously dja
6 matches
Mail list logo