I was wondering whether there would be support for changes to some of the
methods on the field API...
1. Rename `Field._get_val_from_obj` and `Field.value_from_object` methods
These two methods do exactly the same thing (except one returns a default
value if available). In addition, the 'value_
Hi Abhishek,
On Sun, Mar 1, 2015 at 1:16 PM, Abhishek Kumar wrote:
> Hi,
>
> I am Abhishek and am interested in the project titled "SQLAlchemy / NoSQL
> integration". I am good at data-structures and algorithms and have worked
> with C,C++, PHP, Python,C#, Javascript and Mysql. I have an interns
I don't think your problem is related to Django at all, but with the way
that SQL work instead. There's no sense in batch a query that return values
from your DB (unless you're doing 1 query per connection, witch is a stupid
thing to do IMO).
Em sex, 27 de fev de 2015 às 11:18, Ram Rachum escreve
Hi,
I am Abhishek and am interested in the project titled "SQLAlchemy / NoSQL
integration". I am good at data-structures and algorithms and have worked
with C,C++, PHP, Python,C#, Javascript and Mysql. I have an internship
experience at Microsoft, India.
I have some questions which will help m
2015-02-28 22:05 GMT+01:00 Ram Rachum :
> Here is what I'm currently thinking about: Can we make Django do multiple
> separate queries (SQL queries are separated by a semicolon right? Sorry for
> being a noob) and send them one after another before blocking on reading
> any of them? Only then when
On Saturday 28 February 2015 23:05:56 Ram Rachum wrote:
>
> Here is what I'm currently thinking about: Can we make Django do multiple
> separate queries (SQL queries are separated by a semicolon right? Sorry for
> being a noob) and send them one after another before blocking on reading
> any of t
