Re: Accessing 'bytea' field using django.

Thanks all for your comments and suggestions. I will definitely take them into account. -ds99 -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from

Accessing 'bytea' field using django.

access "bytea" type using django. -ds99 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from

Clearing the session on logout.

the row in session table? 2) Is there any way to delete the row after auth.logout() is called? 3) If I do not call auth.logout() and delete the session from that table directly then is it the right approach? Will it have any implications? Thanks, ds99 --~--~-~--~~~---~--

Re: Accessing tables not created by django models using django APIs.

As i said, that was one of the requirements. -ds99 On May 26, 7:38 pm, Reiner wrote: > I don't want to sound rude, I'm just curious, why do you need multiple > tables with the same schema, but different names, in the first place? > > On May 26, 1:17 pm, ds99 wrote: &g

Re: Accessing tables not created by django models using django APIs.

Hi Ankit, Thanks for your comments. -ds99 On May 26, 4:23 pm, Ankit wrote: > ds99 wrote: > > No that table name will be different every time based on some id. If > > table name is same then there is no problem but the issue arises when > > table names are different b

Re: Accessing tables not created by django models using django APIs.

No that table name will be different every time based on some id. If table name is same then there is no problem but the issue arises when table names are different but the schema is same. On May 26, 3:51 pm, Ankit wrote: > ds99 wrote: > > Hi Ankit, > > I got what you are saying

Re: Accessing tables not created by django models using django APIs.

same schema is created for another request. Now to access this table using django APIs, i need to have latest snapshot of the database,i.e, updated model file. For that again we need to fire "python manage.py inspectdb" to create missing models. Is there any other way to do it on the fly?

Re: Accessing tables not created by django models using django APIs.

python script with inspectdb everytime we get a new request? 2) This is possible for only one database as it would inspect database pointed by DATABASE_NAME setting and create models. Can this be done if we have one database per session? Thanks again, ds99 On May 26, 8:13 am, Alex Gaynor wrote

[Urgent]Accessing tables not created by django models using django APIs.

nt to access them to retrieve records using django database APIs. How can i do that? Do i need to add their schema in models.py? Can one model be used to refer to multiple tables in database? Please let me know. Thanks, ds99 --~--~-~--~~~---~--~~ You received this mes