The current mechanism is not optimal but as we discuss works without adding new structure. I am open to proposals.
The way I deal with this is that in models I use the long name for the table db.plugin_tagging_tag but on top of the plugin controller I shorten it tag = db.plugin_tagging_tag Massimo On Dec 23, 10:02 pm, Thadeus Burgess <thade...@thadeusb.com> wrote: > Massimo, > > I know with the current implementation of plugins the current spec > calls for you to append plugin_ to all of the function names / > database names that get called. Is there a better way of doing this? > > The reason I ask is that it leads to having long variable and function > names... a simple query gets quite insane after a while... > > db(db.plugin_pingback_incoming.url == > url)(db.plugin_pingback_incoming.blog_name == > blog_name).select(orderby=~db.plugin_pingback_incoming.receive_date) > > Another annoying issue is the calling internal plugin functions, it > gets just as crazy when you have to call > plugin_pingback_send_pingback(decoder=plugin_pingback_pingback_decoder).... > > Is it feasible that plug-ins could have their own namespace, this way > I can call my function internally "send_pingback" and then in other > parts of the application could access the public functions by > plugin_pingback.send_pingback() ? > > If there is no other way... I will live... > > -Thadeus -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@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.
