|
On Dec 7, 2007, at 8:44 PM, Mike McGonagle wrote:
That is done by sending the [submit( message to the hot inlet. Or do you mean having multiple SQL calls separated by semi-colons? If you wanted to add semicolons, there would have to be a special message, I think we could just reuse the "addsemi", "addcomma", "adddollar" messages from message boxes. As far as I know, the semi-colon at the end of the statement in SQL triggers the execution of that statement, so I can't see an advantage to having multiple, semi-colon terminated statements in a single message box. Does it change how the SQL is executed if they are submitted at the same time?
Any SQL statement would be allowed on the cold inlet. Because of the limitations of Pd (no escape mechanism), and the fact that commas already have a meaning in Pd messages, the hot inlet would not be able to handle commas (unless someone comes up with something quite clever). One advantage of having the second, cold inlet is that it could be devoted to SQL statements, so you don't need to start each message with "sql" and there wouldn't be any words that the [sqlite] object used, like "open", "close", etc. Having the comma handling on the second/cold inlet only means that the first/hot inlet also doesn't need the preceeding "sql" selector since SQL statements will only start with a small set of selectors (CREATE, DROP, INSERT, SELECT, etc). For clarity, I added another cold inlet example and a sketch of building a big query. The big query example in the psql help points out something that I think could get quite confusing, separating the chunks with "sqlend, sql". |
sql-interface.pd
Description: Binary data
.hc ---------------------------------------------------------------------------- News is what people want to keep hidden and everything else is publicity. - Bill Moyers |
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
