Re: new to Django and building web applications. Advice with postgresql

On May 21, 2013, at 8:04 AM, Tom Evans wrote: > > The purpose of using an ORM is to make your application database > agnostic. You should not find that changing DB engine is overly > taxing. Theoretically, yes. The difference between theory and practice is very small in theory, and not so much

Re: new to Django and building web applications. Advice with postgresql

On 21 May 2013 15:00, Tom Evans wrote: > The only queries you need to rewrite on moving django/sqlite -> > django/postgres are raw queries. How many will this beginner have? > Should rewriting raw queries be the thing this beginner worries about? > > 'YMMV' indeed. Switching or changing DB engine

Re: new to Django and building web applications. Advice with postgresql

On Tue, May 21, 2013 at 2:16 PM, Simon Riggs wrote: > On 21 May 2013 13:04, Tom Evans wrote: >> On Sun, May 19, 2013 at 11:51 PM, Scott Anderson >> wrote: >>> On Sunday, May 19, 2013 11:18:07 AM UTC-4, WongoBongo wrote: You don't have to become an expert with postgres to use Django. Yo

Re: new to Django and building web applications. Advice with postgresql

On 21 May 2013 13:04, Tom Evans wrote: > On Sun, May 19, 2013 at 11:51 PM, Scott Anderson > wrote: >> On Sunday, May 19, 2013 11:18:07 AM UTC-4, WongoBongo wrote: >>> >>> You don't have to become an expert with postgres to use Django. You can do >>> most of the db development using SQLite and hol

Re: new to Django and building web applications. Advice with postgresql

On Sunday, May 19, 2013 6:51:09 PM UTC-4, Scott Anderson wrote: > > > I highly recommend *against* waiting for PostgreSQL until deployment. > There are significant differences between SQLite, PostgreSQL, and MySQL. If > you wait until deployment to test on your production database you will find

Re: new to Django and building web applications. Advice with postgresql

On Sun, May 19, 2013 at 11:51 PM, Scott Anderson wrote: > On Sunday, May 19, 2013 11:18:07 AM UTC-4, WongoBongo wrote: >> >> You don't have to become an expert with postgres to use Django. You can do >> most of the db development using SQLite and hold off on postgres until you >> are ready to depl

Re: new to Django and building web applications. Advice with postgresql

On Sunday, May 19, 2013 11:18:07 AM UTC-4, WongoBongo wrote: > You don't have to become an expert with postgres to use Django. You can do > most of the db development using SQLite and hold off on postgres until you > are ready to deploy. I highly recommend *against* waiting for PostgreSQL unt

Re: new to Django and building web applications. Advice with postgresql

You don't have to become an expert with postgres to use Django. You can do most of the db development using SQLite and hold off on postgres until you are ready to deploy. I'd get a Linux server running in VirtualBox. Install Apache and postgres. Configure postgres. Install phpPgAdmin. If you a

Re: new to Django and building web applications. Advice with postgresql

this is the best way - https://django.2scoops.org/, and you can use something like this django template project for your task -h ttps://github.com/nigma/django-modern-template, it have memcached integrated AWS S3 for static files and so on... пят

Re: new to Django and building web applications. Advice with postgresql

you want learn django or postgres ? :-) postgres is cool stuff but it not requited... try this course - https://www.udemy.com/coding-for-entrepreneurs/, (in reddit you can find only 1$

Re: new to Django and building web applications. Advice with postgresql

In addition to installing PostgreSQL you must use tools that come with the postgres installation to 1. create a database (a postgres installation has more than one), 2 create a user (unrelated to user account on the operating system) for django to use (though some people cheat and use the pre-defin