in the databases i have worked with, it is acceptable to quote all data types.
dates escaped or formatted propperly? the dates you are inserting are coming straight from the database so hopefully they are in the right format! If not (for some reason?) you could toss code in there to propperly format the date blobs - not sure, i don't use blobs and I'm not sure what you mean by bound values but if these values are able to be inserted using an insert command, what special formatting has to be done to them? I assume they come out of the database in the correct format and that doing encoding=sql is enough to get them back into the database? text fields that have a comma in the data - if you check the code it is sql encoding every row so it's fine there. I actualy tested my taf with different tables in my database and it worked fine, the only caveat was that tables that had computed columns would have issues since it would try and insert data into those rows but i think that remains a problem even in your example code as well. Pretty sure it works but like i said, I am not familiar with oracle so not sure if there are special rules I am missing. Even so, it should be easy to modify the code to make oracle happy if it needs special attention (: On 7/28/05, Robert Garcia <[EMAIL PROTECTED]> wrote: > I don't think your taf would work, some values would need to be > quoted, and some wouldn't. Also, what about dates? Some may need to > be escaped or formatted properly. What about blobs, or unicode, or > any other data type that wtiango would insert using a bound value. > What about a text field in it, that had a comma in the data. There > are many reasons why this taf wouldn't work. > > To work, I think you would have to also do a select, that your DB > supports, that would describe the fields of the database for you, and > do the appropriate thing in building the insert statement, based on > datatype. You would need to escape any data that could contain a > quote, and think about all of those lovely issues. > > One of the things witango does so nicely for you, is it handles all > of this type of stuff (escaping, bound values, and such) for you in > its DB actions. You lose all of that, and must do yourself, if you > choose to go direct dbms, and MUST think of all the possibilities > that can blow up your statement. > > The reason I suggested VB or RB, is it does all for you (it is > supposed to, I HAVE had to work around a few bugs in the past). > > -- > > Robert Garcia > President - BigHead Technology > VP Application Development - eventpix.com > 13653 West Park Dr > Magalia, Ca 95954 > ph: 530.645.4040 x222 fax: 530.645.4040 > [EMAIL PROTECTED] - [EMAIL PROTECTED] > http://bighead.net/ - http://eventpix.com/ > > On Jul 28, 2005, at 2:08 AM, Alan Wolfe wrote: > > > <sqltest.taf> > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
