On Fri, Oct 2, 2009 at 9:16 PM, adelaide_mike
wrote:
>
> Hi
> In my app the user needs to drill down through a series of templates
> and their views to identify a house. We start with the city, then the
> street and finally the house, in each case chosen from a rendering of
> the possible values
Remember that people often represent their best work, and I bet they
only answer the questions they're most confident about their
experience with.
If you care that much about your code, you'll be fine -- once you have
your 10,000 hours* in as a coder, people will be in awe of your code
to
My only dissatisfaction is that other contributors to this list seem
to do almost anything with very few lines of code, whereas I am using
many. And, being a newbie I naturally worry that I am on the wrong
pathway, having missed the turning.
Thanks to both for your reassurance.
Mike
On Oct 3, 1
Your current approach makes sense. If you're concerned that you're
storing too much data in the session, you could just maintain a
session ID in the session and use that as a key for an sqlite3
database or something, or even a model in your app's database, if that
makes sense. Is there any
Mike,
I think you're doing it right. Unless you want that data to be in the
URL (perhaps) or sent page to page in post data (probably a bad idea)
sessions are your best option.
-David
On Oct 2, 6:16 pm, adelaide_mike wrote:
> Hi
> In my app the user needs to drill down through a series of temp
Hi
In my app the user needs to drill down through a series of templates
and their views to identify a house. We start with the city, then the
street and finally the house, in each case chosen from a rendering of
the possible values selected from the relevant database table.
I have all this worki
6 matches
Mail list logo
