> Maciek wrote: > > By accident I have laerned today that db.execute is not supposed to > > support SELECT query. We have db.select for that. In that case, do we > > call the case closed?
Brad Douglas wrote: > Personally, I'd like db.select merged into db.execute. I don't use the > db.* commands daily and I've fallen into the above case before. > However, I quickly remember the more appropriate usage. > > OTOH, db.execute isn't supposed to return and resulting set, which is > why db.select exists (to my knowledge). I've committed a change in CVS > to db.execute.html noting this and suggests using db.select. IIRC in an old post Radim explained why that must be, but can't find it now. > I would consider this closed. still outstanding: db.execute needs to throw an error- not segfault -when passed SELECT. Hamish _______________________________________________ grass-dev mailing list [email protected] http://grass.itc.it/mailman/listinfo/grass-dev
