Re: [snapdal-devel] Stored Statement names

[Philip N. <pan...@ya...>]

Look for a file called Statements.xml as an example. This allows all the
statments to be in a single file. In addition, you can use include statements
in Statements.xml if you want to separate them out by certain functions.

In the version I will release "real soon now" you can also specify a class that
has the statements defined in them in code. Some people don't like config files
so first it was a way to accomodate that, but more importantly, it was for
autogenerated statements. For example, there really is no need to have
statement files when you can just ask the database for a list of stored
procedures and build them on the fly.

This release also has a tool that will generate statement files from stored
procedures or tables. Actually, your release has much of the code, but the new
release has a fairly usable tool.

--- Cory Foy <Cor...@mo...> wrote:

> Ok, second question. :)
> 
> For the stored statements, is there a way to define them all in one 
> file? Right now it seems like if I wanted to create a DataAdapter that 
> used all CRUD operations from a stored file, I'd have to have four 
> seperate files. Is there something else I'm missing?
> 
> Cory
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by Yahoo.
> Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
> Search APIs Find out how you can build Yahoo! directly into your own
> Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
> _______________________________________________
> Snapdal-devel mailing list
> Sna...@li...
> https://lists.sourceforge.net/lists/listinfo/snapdal-devel
> 


Philip - http://blogs.xcskiwinn.org/panmanphil
"There's a difference between righteous anger and just being crabby" - Barbara