On 19-6-2012 9:46, Laurence MacNeill wrote:
> On Monday, June 18, 2012, Melvyn Sopacua wrote:
>
>> On 18-6-2012 9:52, Laurence MacNeill wrote:
>>> well -- I hit the wrong key and posted that before I was finished
>> typing...
>>>
>>> here's what's in my views.py file:
>>> def index(request)
>>>
Right -- different tables in the same database, of course... Thanks.
L.
On Monday, June 18, 2012, Daniel Roseman wrote:
> On Monday, 18 June 2012 08:40:53 UTC+1, Laurence MacNeill wrote:
>>
>> Ok, I'm a total django noob here, so I am probably doing this wrong...
>> But here goes...
>>
>> When
On Monday, June 18, 2012, Melvyn Sopacua wrote:
> On 18-6-2012 9:52, Laurence MacNeill wrote:
> > well -- I hit the wrong key and posted that before I was finished
> typing...
> >
> > here's what's in my views.py file:
> > def index(request)
> > current_username = os.environ['REMOTE_USER']
>
On Mon, Jun 18, 2012 at 1:45 PM, Dennis Lee Bieber wrote:
>
>
> First, is everybody on the same page (terminology)... (Independent
> of Django)
>
>First is: multiple database engines (SQLite3, MySQL, Access/JET,
> etc.). Working across multiple engines is never easy -- one typically
>
> On Mon, Jun 18, 2012 at 9:30 AM, Daniel Roseman
> wrote:
There are certain "advanced" features of Django - multiple DBs, model
> subclassing, that sort of thing
I feel there's quite a few problems that would be relatively unsolvable
without model subclassing. At least in any efficient way.
On Monday, 18 June 2012 13:16:55 UTC+1, lawgon wrote:
>
> On Mon, 2012-06-18 at 05:12 -0700, Daniel Roseman wrote:
> > Multiple databases is a whole different
> > question, which you really don't want to get into as a newbie (or,
> > indeed,
> > at all if possible).
>
> could you elaborate on
On Mon, 2012-06-18 at 05:12 -0700, Daniel Roseman wrote:
> Multiple databases is a whole different
> question, which you really don't want to get into as a newbie (or,
> indeed,
> at all if possible).
could you elaborate on this - I was thinking on getting into multiple
databases and would appr
On Monday, 18 June 2012 08:40:53 UTC+1, Laurence MacNeill wrote:
>
> Ok, I'm a total django noob here, so I am probably doing this wrong...
> But here goes...
>
> When someone comes to my django app's root (index), I need to verify their
> user-name (which is stored in a Linux environment variab
On 18-6-2012 9:52, Laurence MacNeill wrote:
> well -- I hit the wrong key and posted that before I was finished typing...
>
> here's what's in my views.py file:
> def index(request)
> current_username = os.environ['REMOTE_USER']
And you're sure this works? Try:
return django.shortcuts.rend
well -- I hit the wrong key and posted that before I was finished typing...
here's what's in my views.py file:
def index(request)
current_username = os.environ['REMOTE_USER']
This should provide me with their username (yes I do have 'import os' at
the top of the file)...
Now, after I get
Ok, I'm a total django noob here, so I am probably doing this wrong... But
here goes...
When someone comes to my django app's root (index), I need to verify their
user-name (which is stored in a Linux environment variable). Based on
where (or if) I find their user-name, I want to send them to
11 matches
Mail list logo
