Comments on: It Just Works http://pocoproject.org/blog/?p=115 News and discussion for the POCO Community Thu, 09 May 2013 12:05:16 +0200 http://wordpress.org/?v=2.8.5 hourly 1 By: alex http://pocoproject.org/blog/?p=115&cpage=1#comment-311 alex Fri, 08 Feb 2008 00:29:32 +0000 http://pocoproject.org/poco/blog/?p=115#comment-311 Mike, I gave it a bit of thought today and it may actually be easier than I originally thought. Would you be willing to put in some work and turn it into an actual feature? Alex Mike,

I gave it a bit of thought today and it may actually be easier than I originally thought. Would you be willing to put in some work and turn it into an actual feature?

Alex

]]> By: alex http://pocoproject.org/blog/?p=115&cpage=1#comment-310 alex Thu, 07 Feb 2008 00:58:46 +0000 http://pocoproject.org/poco/blog/?p=115#comment-310 This is easily doable for POD bindings and some databases (SQLite for sure), but the only truly portable way across all databases that I can think of would be to massage the SQL string and replace the placeholders before execution or turn placeholders into question marks and provide sufficient amount of bindings. Things then get more complicated when bindings are containers or complex types such as tuples or objects. Even more complicated for containers of tuples or objects. And yet more complicated for bulk execution. The solution I'd be willing to add as a feature should work in all of the above cases. Alex This is easily doable for POD bindings and some databases (SQLite for sure), but the only truly portable way across all databases that I can think of would be to massage the SQL string and replace the placeholders before execution or turn placeholders into question marks and provide sufficient amount of bindings. Things then get more complicated when bindings are containers or complex types such as tuples or objects. Even more complicated for containers of tuples or objects. And yet more complicated for bulk execution. The solution I’d be willing to add as a feature should work in all of the above cases.

Alex

]]> By: mike http://pocoproject.org/blog/?p=115&cpage=1#comment-309 mike Wed, 06 Feb 2008 21:53:35 +0000 http://pocoproject.org/poco/blog/?p=115#comment-309 Do you plan to support binding by name? Something like this: string addr = "..."; session << "update person " "set main_address = :addr, contact_address = :addr " "where id = 7", use(addr, "addr"), now; It is very useful --- never make an error in order of parameters. If it can be implemented as some extension of existing implementation please let me know. Do you plan to support binding by name?

Something like this:

string addr = “…”;
session << “update person ”
“set main_address = :addr, contact_address = :addr ”
“where id = 7″,
use(addr, “addr”), now;

It is very useful — never make an error in order of parameters.

If it can be implemented as some extension of existing implementation please let me know.

]]> By: alex http://pocoproject.org/blog/?p=115&cpage=1#comment-301 alex Wed, 16 Jan 2008 03:39:12 +0000 http://pocoproject.org/poco/blog/?p=115#comment-301 It absolutely would. Anyone willing to contribute ? ;-) (it's only two virtual functions, see the sample). In the meantime, few data modifications: <ul> <li>fix for <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=1871946&group_id=132964&atid=725709" rel="nofollow">this</a> SF bug report</li> <li>use() takes reference now (this may break some code that should have been broken in the first place)</li> <li>bind() for constants (this is for const char* and other consts - it'll make an internal copy of the value)</li> <li>Statement: allow for easier external binding supply (this is for Brad, I hope it makes him happy ;-)</li> </ul> Alex It absolutely would. Anyone willing to contribute ? ;-) (it’s only two virtual functions, see the sample).

In the meantime, few data modifications:

  • fix for this SF bug report
  • use() takes reference now (this may break some code that should have been broken in the first place)
  • bind() for constants (this is for const char* and other consts – it’ll make an internal copy of the value)
  • Statement: allow for easier external binding supply (this is for Brad, I hope it makes him happy ;-)

Alex

]]> By: paschal http://pocoproject.org/blog/?p=115&cpage=1#comment-302 paschal Tue, 15 Jan 2008 19:00:10 +0000 http://pocoproject.org/poco/blog/?p=115#comment-302 This would also be cool in my opinion std::cout << RecordSet(session, "SELECT * FROM Simpsons", new JSONFormatter()); paschal. This would also be cool in my opinion

std::cout << RecordSet(session, “SELECT * FROM Simpsons”, new JSONFormatter());

paschal.

]]> By: alex http://pocoproject.org/blog/?p=115&cpage=1#comment-303 alex Sat, 12 Jan 2008 18:57:20 +0000 http://pocoproject.org/poco/blog/?p=115#comment-303 Few additions to Data SVN trunk: <ul> <li>SQL logging channel and archiving strategy</li> <li>row formatting refactored</li> <li>affected row count for insert, delete and update returned from Statement::execute()</li> <li>internal SQL string formatting capability using Poco::format()</li> </ul> Few additions to Data SVN trunk:

  • SQL logging channel and archiving strategy
  • row formatting refactored
  • affected row count for insert, delete and update returned from Statement::execute()
  • internal SQL string formatting capability using Poco::format()
]]> By: alex http://pocoproject.org/blog/?p=115&cpage=1#comment-304 alex Fri, 11 Jan 2008 12:08:37 +0000 http://pocoproject.org/poco/blog/?p=115#comment-304 James, While talking to other projects and trying to merge may seem like a good idea initially, it is our experience that usually it does not bear much fruit and proves to be a waste of time. We tried it with <a href="http://soci.sourceforge.net/" rel="nofollow">SOCI</a> and <a href="http://pt-framework.sourceforge.net/" rel="nofollow">Platinum</a>. The main reason for failure is that ultimately none of the options turns out to be aceptable for both sides. Merging is a tough thing and people (including us) usually stick strongly to their code. While I may be willing to consider molding <a href="http://poco.svn.sourceforge.net/viewvc/poco/sandbox/Servlet/" rel="nofollow">PocoServlet</a> code to meet <a href="http://www.total-knowledge.com" rel="nofollow">Total Knowledge</a> half way, I would not be willing to give up Poco::Net dependency in favor of socket++ and would not be willing to have firm Apache dependency. That being said, we are very interested in your fastCGI code (I had plans myself for it) - it would be a nice addition to the servlet library, so if you are willing to contribute it, by all means do so. Recently, Paschal has ported all the Tomcat samples (I'll submit them, I hope, this weekend) to SVN. Also, this reply is by no means meant to discourage you to talk to CppServ folks. Please do talk to them if you have time and enthusiasm, but be aware what you may be facing. Alex James,

While talking to other projects and trying to merge may seem like a good idea initially, it is our experience that usually it does not bear much fruit and proves to be a waste of time. We tried it with SOCI and Platinum. The main reason for failure is that ultimately none of the options turns out to be aceptable for both sides. Merging is a tough thing and people (including us) usually stick strongly to their code. While I may be willing to consider molding PocoServlet code to meet Total Knowledge half way, I would not be willing to give up Poco::Net dependency in favor of socket++ and would not be willing to have firm Apache dependency. That being said, we are very interested in your fastCGI code (I had plans myself for it) – it would be a nice addition to the servlet library, so if you are willing to contribute it, by all means do so. Recently, Paschal has ported all the Tomcat samples (I’ll submit them, I hope, this weekend) to SVN.

Also, this reply is by no means meant to discourage you to talk to CppServ folks. Please do talk to them if you have time and enthusiasm, but be aware what you may be facing.

Alex

]]> By: James Mansion http://pocoproject.org/blog/?p=115&cpage=1#comment-305 James Mansion Fri, 11 Jan 2008 11:17:41 +0000 http://pocoproject.org/poco/blog/?p=115#comment-305 Can't help thinking that it would be worth talking to these guys http://www.total-knowledge.com/progs/cppserv/ if there are any issues relating to creating de-factor standards for this sort of thing. Note to self: have a POCO port of libFastCGI: must send it along. Can’t help thinking that it would be worth talking to these guys http://www.total-knowledge.com/progs/cppserv/ if there are any issues relating to creating de-factor standards for this sort of thing.

Note to self: have a POCO port of libFastCGI: must send it along.

]]> By: Paschal http://pocoproject.org/blog/?p=115&cpage=1#comment-308 Paschal Mon, 07 Jan 2008 00:25:10 +0000 http://pocoproject.org/poco/blog/?p=115#comment-308 Just tuned in! This is simply exciting news. HTTPServer, Servlets and now Server Pages ... should this be called CSP ?. C++ has finally joined the internet party in a big way.. because of Poco. You guys are geniuses. Just tuned in!
This is simply exciting news. HTTPServer, Servlets and now Server Pages … should this be called CSP ?. C++ has finally joined the internet party in a big way.. because of Poco.

You guys are geniuses.

]]> By: alex http://pocoproject.org/blog/?p=115&cpage=1#comment-306 alex Sun, 06 Jan 2008 22:52:31 +0000 http://pocoproject.org/poco/blog/?p=115#comment-306 Ah great. I thought about it long time ago, in my servlet days. So, your page compiler, in turn, will work great with the servlets. Paschal, are you tuned in? Ah great. I thought about it long time ago, in my servlet days. So, your page compiler, in turn, will work great with the servlets.

Paschal, are you tuned in?

]]>