On Jan 5, 6:40 pm, Petite Abeille wrote:
> On Jan 6, 2012, at 12:13 AM, Chris Kavanagh wrote:
>
> > I believe, thanks to your (previous) post, I was confused as to the
> > difference between SQL and Database in general. I had thought learning
> > SQL was learning database design. When in actuali
On Jan 6, 2012, at 12:13 AM, Chris Kavanagh wrote:
> I believe, thanks to your (previous) post, I was confused as to the
> difference between SQL and Database in general. I had thought learning
> SQL was learning database design. When in actuality, it's just the
> language used to access database
On Jan 5, 2:54 pm, Lie Ryan wrote:
> On 01/06/2012 02:35 AM, Dennis Lee Bieber wrote:
>
> > Django's models are just a means to define those independent of engine
> > specific notation.
>
> while introducing django-specific notation, which generally maps more
> neatly to the theoretical foundati
On Jan 5, 10:35 am, Dennis Lee Bieber wrote:
> On Wed, 4 Jan 2012 17:50:41 -0800 (PST), Chris Kavanagh
>
> While my comment regarding MVC has been shot down by others, I'll
> still stand by the comment regarding relational database theory: the
> first three Codd Normal Forms and related
On Jan 5, 3:58 am, Lie Ryan wrote:
> On 01/05/2012 01:01 PM, Chris Kavanagh wrote:
>
>
> While learning SQL could be helpful for writing fine-tuned SQL queries,
> IMO it doesn't really help much to design an effective database. To
> design an effective database schema, you need to learn about da
On 01/06/2012 02:35 AM, Dennis Lee Bieber wrote:
Django's models are just a means to define those independent of engine
specific notation.
while introducing django-specific notation, which generally maps more
neatly to the theoretical foundation than SQL (while SQL maps more
neatly to the imp
On 01/05/2012 01:01 PM, Chris Kavanagh wrote:
On Jan 4, 8:20 am, Andre Terra wrote:
I'm sorry, folks, but I'll have to *vehemently **disagree *with a lot of
what has been said in this thread. To the OP, I'm sorry I didn't reply any
sooner.
No, you *don't need *to go reading about what MVC me
On Wed, 2012-01-04 at 11:20 -0200, Andre Terra wrote:
> I'm sorry, folks, but I'll have to vehemently disagree with a lot of
> what has been said in this thread. To the OP, I'm sorry I didn't reply
> any sooner.
>
> No, you don't need to go reading about what MVC means. Django is a MTV
> framework
On Jan 4, 10:36 am, Javier Guerra Giraldez wrote:
> On Wed, Jan 4, 2012 at 8:20 AM, Andre Terra wrote:
> > No, you don't need to go reading about what MVC means. Django is a MTV
> > framework, not MVC. There are similarities, but the differences are enough
> > to confuse your head if this is yo
On Jan 4, 9:16 am, Venkatraman S wrote:
> On Wed, Jan 4, 2012 at 6:50 PM, Andre Terra wrote:
> > You won't need to write raw SQL in Django until you've reached a big
> > bottleneck, and one that can't be solved in any other way. Writing raw SQL
> > is exactly what Django wants you to *stop* doi
On Jan 4, 8:20 am, Andre Terra wrote:
> I'm sorry, folks, but I'll have to *vehemently **disagree *with a lot of
> what has been said in this thread. To the OP, I'm sorry I didn't reply any
> sooner.
>
> No, you *don't need *to go reading about what MVC means. Django is a
> *MTV *framework,
> no
On Jan 3, 11:40 pm, Dennis Lee Bieber wrote:
> On Tue, 3 Jan 2012 19:30:37 -0800 (PST), Chris Kavanagh
>
> wrote:
>
> >Well, I was referring to the database part, but really I need to learn
> >more about web development too. I know HTML, CSS, JavaScript vaguely,
> >and that's about it. Since I
On Wed, Jan 4, 2012 at 8:20 AM, Andre Terra wrote:
> No, you don't need to go reading about what MVC means. Django is a MTV
> framework, not MVC. There are similarities, but the differences are enough
> to confuse your head if this is your first time with either one.
I agree, i'd even say forget
On Wed, Jan 4, 2012 at 12:16 PM, Venkatraman S wrote:
> SQL is highly flexible provided you know to write good sql (its like the
> way Russell mentions 'It Depends' :P ); atleast i have been writing sqls
> for the past 8 years and i find it easy to write them when the
> relationships are complex.
On Wed, Jan 4, 2012 at 6:50 PM, Andre Terra wrote:
> You won't need to write raw SQL in Django until you've reached a big
> bottleneck, and one that can't be solved in any other way. Writing raw SQL
> is exactly what Django wants you to *stop* doing. The ORM doesn't only
> exist in order to speed
I'm sorry, folks, but I'll have to *vehemently **disagree *with a lot of
what has been said in this thread. To the OP, I'm sorry I didn't reply any
sooner.
No, you *don't need *to go reading about what MVC means. Django is a
*MTV *framework,
not *MVC*. There are similarities, but the differences a
On Jan 3, 5:58 pm, Python_Junkie
wrote:
> Don't want to confuse you on the database topic, but thought I would
> add my 2 cents.
>
> You asked how to go about learning how to design / utilize the
> database within the context of django.
>
> I just wanted to point out that the django tutorial wil
On Jan 3, 4:09 am, wC wrote:
> Chris,
>
> I think was somehow in the same stage not so long ago... Here is how I went
> about it:
>
> 1. I watched a db-class video from time to time (teaches you what joins are
> etcetera). Using the ORM without db knowledge is ok if efficiency is not
> your main
On Jan 2, 8:49 pm, Victor Hooi wrote:
> Hi,
>
> Do you mean learning more about Django in general, or about the
> models.py/database portion specifically?
>
> If you haven't done much web-development before, or used any MVC
> frameworks, I suggest you start by reading up on those - there's plent
On Jan 2, 7:38 pm, Mike Dewhirst wrote:
> On 3/01/2012 10:59am, Chris Kavanagh wrote:
>
>
>
>
>
>
>
>
>
>
>
> > On Jan 2, 6:57 pm, Chris Kavanagh wrote:
> >> I'm new to django& programming in general. I know the basics of
> >> Python. Anyways, going through the djangoproject tutorial, I came t
Don't want to confuse you on the database topic, but thought I would
add my 2 cents.
You asked how to go about learning how to design / utilize the
database within the context of django.
I just wanted to point out that the django tutorial will point you
down the road of implementing a database a
Chris,
I think was somehow in the same stage not so long ago... Here is how I went
about it:
1. I watched a db-class video from time to time (teaches you what joins are
etcetera). Using the ORM without db knowledge is ok if efficiency is not
your main concern. Sooner or later you have to make
Hi,
Do you mean learning more about Django in general, or about the
models.py/database portion specifically?
If you haven't done much web-development before, or used any MVC
frameworks, I suggest you start by reading up on those - there's plenty of
guides to that online.
In terms of learning
On 3/01/2012 10:59am, Chris Kavanagh wrote:
On Jan 2, 6:57 pm, Chris Kavanagh wrote:
I'm new to django& programming in general. I know the basics of
Python. Anyways, going through the djangoproject tutorial, I came to
the part where you edit the polls/models.py, and this is where I need
advi
On Jan 2, 6:57 pm, Chris Kavanagh wrote:
> I'm new to django & programming in general. I know the basics of
> Python. Anyways, going through the djangoproject tutorial, I came to
> the part where you edit the polls/models.py, and this is where I need
> advice.
>
> I understand roughly what's goi
I'm new to django & programming in general. I know the basics of
Python. Anyways, going through the djangoproject tutorial, I came to
the part where you edit the polls/models.py, and this is where I need
advice.
I understand roughly what's going in when we write the script in
models.py, however if
26 matches
Mail list logo
