It is not a bug. db(query)
query can be a DAL query or a SQL query (string). mind that what are you doing is dangerous unless you have a way to restrict who can access that xmlrpc function to the administrator. On Aug 17, 3:29 pm, rb <rbspg...@gmail.com> wrote: > In my client code (of my thick xmlrpc client) I perform a Read (or > Select) with code, some of which follows: > > --- > def Read( self, keyName="pri", maxRowCount=0): > keyColNames = self.tblInfo.GetKeyColNames(keyName) > keySegValues = self.record.GetNonNullColValues (keyColNames) > if len(keySegValues) < 1: > # rowSelectStr = "db." + self.tblVname + ".id>0" > rowSelectStr = self.tblVname + ".id>0" > else: > --- > > In the above code, rowSelectStr is sent to the svr to be put inside of > a db(eval(rowSelectStr)).select() call (I'm only including relevant > code here). Notice the commented out line and the line that follows. > > Originally this code sat in a module on the svr and the commented-out > line worked fine. But when I sent it over xmlrpc from the client it > failed. Digging into the gluon code (sql.py , I think) I saw that the > parsing code that was picking out the tables was getting TWO tables: > 'tblVname' and 'db' - and it choked on this. I found that just > removing the db. from the front of the tablename string worked. > > Is this a bug? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
