On 4 dic, 17:17, mdipierro <mdipie...@cs.depaul.edu> wrote: > There is not trivial solution since different databases handle blobs > in different ways (which is why web2py normally base64 encodes them) > and there are issues with escaping and encoding. If you do not need > that column, I suggest use a sql view to eliminate it. If you do need > it, you may try create a SQLCustomField. > > I will think a more general solution.
Why isn't a SQLCustomType a general enough solution?. -- 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.
