Re: Missing peice before best practises

On Monday, July 1, 2013, Tom Evans wrote:

On Mon, Jul 1, 2013 at 11:37 AM, Sayth Renshaw <flebber.crue@gmail.com> wrote:
> Is that good though?
>
> Barring 2 scoops there is no new material to recognise and guide users to
> the new features of Django and to get beginner Django developers on board
> quicker.
>
> It leads to bits of info for each python framework but nothing
> comprehensive.
>
> Sayth
>

Virtualenv, pip etc are not features of Django, they are features of
python. It is right that Django mentions them in places, it is doubly
right that it does not attempt to duplicate the fine documentation
that pip and virtualenv possess themselves.

Cheers

Tom

Agreed good tutorials would show steps and then point to resources for further reading,

At this point though it appears there is a scarcity of good tutorials for current Django.

Sayth

 

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

no style in admin pages; learning from djangobook.com

Hi all,
Just getting started with Django.
I'm following the projects on djangobook.com.
After activating the admin interface I don't have .css styling.
I also have no idea how to enable it.
Any help is greatly appreciated.
Thanks!

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: data transfer between databases

On 1 July 2013 13:02, Mike Dewhirst <miked@dewhirst.com.au> wrote:

 

On 1/07/2013 9:35pm, Tom Evans wrote:

On Sun, Jun 30, 2013 at 11:24 PM, Mike Dewhirst <miked@dewhirst.com.au> wrote:

mulianto and Avraham

Thanks for your suggestions. Dumping data isn't the entire problem - which
is this:

There will be an *ongoing* need to add new data from tables in one database
to the same-named tables in another database on a remote machine. Two of the
tables are in a m2m relationship.

You can use direct access via "foreign tables" the name of the Postgres distributed database feature.

http://www.postgresql.org/docs/devel/static/sql-createforeigntable.html

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: data transfer between databases

Tom

I'm not a DBA so I'll need to do some quiet study of those references.
Thanks for that.

Cheers

Mike

On 1/07/2013 9:35pm, Tom Evans wrote:
> On Sun, Jun 30, 2013 at 11:24 PM, Mike Dewhirst <miked@dewhirst.com.au> wrote:
>> mulianto and Avraham
>>
>> Thanks for your suggestions. Dumping data isn't the entire problem - which
>> is this:
>>
>> There will be an *ongoing* need to add new data from tables in one database
>> to the same-named tables in another database on a remote machine. Two of the
>> tables are in a m2m relationship.
>>
>
> Sounds like you want replication from one database to another. Recent
> versions of Postgres have built in support for what they call "log
> shipping" or "streaming replication", where logs of updates are
> transferred to backup servers and executed:
>
> http://www.postgresql.org/docs/current/static/warm-standby.html
>
> This requires some manual setup of your servers to transfer the logs.
>
> There are other forms of replication, postgresql actually provide a
> useful table listing the various solutions, their pros/cons, and links
> on how to implement them. Lots of the solutions are not part of
> postgresql itself, but use third party packages like slony to effect
> the replication. See here:
>
> http://www.postgresql.org/docs/current/static/different-replication-solutions.html
>
> Cheers
>
> Tom
>

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: data transfer between databases

On Sun, Jun 30, 2013 at 11:24 PM, Mike Dewhirst <miked@dewhirst.com.au> wrote:
> mulianto and Avraham
>
> Thanks for your suggestions. Dumping data isn't the entire problem - which
> is this:
>
> There will be an *ongoing* need to add new data from tables in one database
> to the same-named tables in another database on a remote machine. Two of the
> tables are in a m2m relationship.
>

Sounds like you want replication from one database to another. Recent
versions of Postgres have built in support for what they call "log
shipping" or "streaming replication", where logs of updates are
transferred to backup servers and executed:

http://www.postgresql.org/docs/current/static/warm-standby.html

This requires some manual setup of your servers to transfer the logs.

There are other forms of replication, postgresql actually provide a
useful table listing the various solutions, their pros/cons, and links
on how to implement them. Lots of the solutions are not part of
postgresql itself, but use third party packages like slony to effect
the replication. See here:

http://www.postgresql.org/docs/current/static/different-replication-solutions.html

Cheers

Tom

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Missing peice before best practises

On Mon, Jul 1, 2013 at 11:37 AM, Sayth Renshaw <flebber.crue@gmail.com> wrote:
> Is that good though?
>
> Barring 2 scoops there is no new material to recognise and guide users to
> the new features of Django and to get beginner Django developers on board
> quicker.
>
> It leads to bits of info for each python framework but nothing
> comprehensive.
>
> Sayth
>

Virtualenv, pip etc are not features of Django, they are features of
python. It is right that Django mentions them in places, it is doubly
right that it does not attempt to duplicate the fine documentation
that pip and virtualenv possess themselves.

Cheers

Tom

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
For more options, visit https://groups.google.com/groups/opt_out.

Not showing a model from the models' list in admin

Issuing the "localhost:8000/admin" request in the browser I am presented with the list of all registered models.
I don't want one of this models to be visualized in that list even though it is widely used and referenced by other models.
How can I do that without unregistering the model?

Ciao
Vittorio

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
For more options, visit https://groups.google.com/groups/opt_out.