Two thoughts:
1. If you are analysing tweets, why are you deleting on a daily basis?
Wouldn't a longer term view give you a better picture?
2. Why not use the status_id field from the tweet as your id? The twitter
have the problem of dealing with it's size, and you will (should, or at
least could
On Mon, Aug 5, 2013 at 4:52 PM, Sean Whalen wrote:
> How can the models be configured to use bigserial? I know I could convert
> the tables myself, but that is not helpful for distributing the app.
https://docs.djangoproject.com/en/1.5/ref/django-admin/#sqlcustom-appname-appname
you can provide
On Mon, 5 Aug 2013 14:26:00 -0700 (PDT)
Sean Whalen wrote:
> I have a Django/PostgreSQL application to analyze data from tweets. The
> dataset increases by thousands of records with each request. I am using
> the database primarily as a relational cache, so I had planned to delete
> all records
How can the models be configured to use bigserial? I know I could convert
the tables myself, but that is not helpful for distributing the app.
It looks like someone requested that feature three years ago.
https://code.djangoproject.com/ticket/14286
On Mon, Aug 5, 2013 at 5:36 PM, Javier Guerra
On Mon, Aug 5, 2013 at 4:26 PM, Sean Whalen wrote:
> However, because the Django ORM uses the SERIAL data type to store the IDs
> in the DB; the IDs get larger, even when all existing records have been
> deleted. Eventually, I will run out of key space. What can I do to make
> Django produce small
I have a Django/PostgreSQL application to analyze data from tweets. The
dataset increases by thousands of records with each request. I am using the
database primarily as a relational cache, so I had planned to delete all
records every 24 hours to permit new requests, without needlessly
increasi
6 matches
Mail list logo
