Yarin Hello, good afternoon, I take your question to answer in general
terms as used in web2py Procedures.
1- sure that the database engine you use supports stored procedures (ex:
mysql, postgresql, Sybase, Oracle, etc).
2- must create the procedure in the database using the SQL client that
Hi,
I've read this section on the manual several times (
http://www.web2py.com/books/default/chapter/29/06/the-database-abstraction-layer#executesql),
but wasn't able to understand its meaning.
The reason is that the first three lines are missing, letting the text
without the explanation of
+1
--
Because experiencing your loyal love is better than life itself,
my lips will praise you. (Psalm 63:3)
--
We just added it a couple days ago. If you get a chance to try it, let us
know if there are any problems.
Anthony
On Sunday, August 26, 2012 8:55:52 PM UTC-4, Andrew wrote:
Thanks Anthony, Wasn't aware of that one, and it looks quite useful.
On Monday, August 27, 2012 6:29:55 AM UTC+12,
Often wondered about this too. You would also have to call them with
executesql.
So should the dal API support stored procedure , database macro definitions and
execution?
Would require work in each database adapter, but could we come up with a single
interface ?
--
Often wondered about this too. You would also have to call them with
executesql.
So should the dal API support stored procedure , database macro
definitions and execution?
Would require work in each database adapter, but could we come up with a
single interface ?
Do you mean for
Thanks Anthony, Wasn't aware of that one, and it looks quite useful.
On Monday, August 27, 2012 6:29:55 AM UTC+12, Anthony wrote:
Often wondered about this too. You would also have to call them with
executesql.
So should the dal API support stored procedure , database macro
definitions
+1
On Sun, Aug 26, 2012 at 8:55 PM, Andrew awillima...@gmail.com wrote:
Thanks Anthony, Wasn't aware of that one, and it looks quite useful.
On Monday, August 27, 2012 6:29:55 AM UTC+12, Anthony wrote:
Often wondered about this too. You would also have to call them with
executesql.
Do they need to be created dynamically by your app? If not, you could just
create them outside of web2py.
Side note -- if you want web2py to generate SQL for any queries, you can
form the queries as usual and call the ._select() method instead of
.select() -- that will return the SQL as a
Yeah I could create them outside of web2py, was just wondering if there was
a good way to perform SQL 'prep' on a db along with the table migrations..
not critical though.
On Sat, Aug 25, 2012 at 6:29 PM, Anthony abasta...@gmail.com wrote:
Do they need to be created dynamically by your app? If
I suppose executesql would be fine in that case if you want to do it that
way.
On Saturday, August 25, 2012 6:34:18 PM UTC-4, Yarin wrote:
Yeah I could create them outside of web2py, was just wondering if there
was a good way to perform SQL 'prep' on a db along with the table
migrations..
11 matches
Mail list logo
