Re: SQL Support in 6.0

This WebDNA talk-list message is from

2004


It keeps the original formatting.
numero = 56181
interpreted = N
texte = >=20 > Are you referring to the old [SQL] context? The new SQL contexts does = not > use ODBC to communicate with a MySQL server. No. I am referring to the new commands. And the question was about = MSSQL, not MySQL. If I execute this: [SQLExecute ref=3DMyConnection&var=3DMyResults] exec getAuthorsAndBooks @AuthorName =3D 'Smith' [/SQLExecute] And the Stored Procedure named getAuthorsAndBooks looks something like = this: CREATE PROC getAuthorsAndBooks=20 @Author varchar(20) AS=20 Select FirstName, LastName from Authors WHERE Author =3D @AuthorName Select Title from Books WHERE Author =3D @AuthorName GO How does the SQLResults parse the two different results sets? Also, if I happen to put in invalid SQL, like this: [SQLExecute ref=3DMyConnection&var=3DMyResults] exec getAuthorsAndBooks @AuthorName =3D Smith [/SQLExecute] Does that mean that the Server Message gets returned where the = 'SQLExecute' command is on my WebDNA page?=20 "Server: Msg 207, Level 16, State 3, Line 1 Invalid column name 'johnson'." And, again, what is the timeline for supporting MSSQL with these new = commands?=20 Thanks. - Trevor >=20 > -----Original Message----- > From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of > Crist, Trevor > Sent: Tuesday, February 17, 2004 11:50 AM > To: WebDNA Talk > Subject: SQL Support in 6.0 >=20 >=20 > What is the timeline for support of MSSQL? >=20 > Also, I don't see any way for the new SQL features to handle: > - Returns of multiple rowsets (typical when executing a stored = procedure) > - Ability to handle error and other message types that are generated = by > the SQL server. >=20 > These two issues in my mind are the biggest limitations with WebCat's = SQL > support (aside from the ODBC bottlenecks). >=20 > Are there plans to add this support? If so, what is the timeline? >=20 > We have begun moving much of our system over to .asp. However, if = these > features are supported, we will buy version 6 and keep on using = WebDNA. >=20 > Thanks. >=20 > - Trevor >=20 >=20 >=20 > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.572 / Virus Database: 362 - Release Date: 1/27/2004 >=20 >=20 > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to digest@talk.smithmicro.com> > Web Archive of this list is at: http://webdna.smithmicro.com/ >=20 > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to digest@talk.smithmicro.com> > Web Archive of this list is at: http://webdna.smithmicro.com/ >=20 > --- > Incoming mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.572 / Virus Database: 362 - Release Date: 1/27/2004 >=20 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.572 / Virus Database: 362 - Release Date: 1/27/2004 =20 ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: SQL Support in 6.0 ( "Steve Contreras" 2004)
  2. Re: SQL Support in 6.0 ( "Crist, Trevor" 2004)
  3. Re: SQL Support in 6.0 ( "Scott Anderson" 2004)
  4. SQL Support in 6.0 ( "Crist, Trevor" 2004)
>=20 > Are you referring to the old [SQL] context? The new SQL contexts does = not > use ODBC to communicate with a MySQL server. No. I am referring to the new commands. And the question was about = MSSQL, not MySQL. If I execute this: [SQLExecute ref=3DMyConnection&var=3DMyResults] exec getAuthorsAndBooks @AuthorName =3D 'Smith' [/SQLExecute] And the Stored Procedure named getAuthorsAndBooks looks something like = this: CREATE PROC getAuthorsAndBooks=20 @Author varchar(20) AS=20 Select FirstName, LastName from Authors WHERE Author =3D @AuthorName Select Title from Books WHERE Author =3D @AuthorName GO How does the SQLResults parse the two different results sets? Also, if I happen to put in invalid SQL, like this: [SQLExecute ref=3DMyConnection&var=3DMyResults] exec getAuthorsAndBooks @AuthorName =3D Smith [/SQLExecute] Does that mean that the Server Message gets returned where the = 'SQLExecute' command is on my WebDNA page?=20 "Server: Msg 207, Level 16, State 3, Line 1 Invalid column name 'johnson'." And, again, what is the timeline for supporting MSSQL with these new = commands?=20 Thanks. - Trevor >=20 > -----Original Message----- > From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of > Crist, Trevor > Sent: Tuesday, February 17, 2004 11:50 AM > To: WebDNA Talk > Subject: SQL Support in 6.0 >=20 >=20 > What is the timeline for support of MSSQL? >=20 > Also, I don't see any way for the new SQL features to handle: > - Returns of multiple rowsets (typical when executing a stored = procedure) > - Ability to handle error and other message types that are generated = by > the SQL server. >=20 > These two issues in my mind are the biggest limitations with WebCat's = SQL > support (aside from the ODBC bottlenecks). >=20 > Are there plans to add this support? If so, what is the timeline? >=20 > We have begun moving much of our system over to .asp. However, if = these > features are supported, we will buy version 6 and keep on using = WebDNA. >=20 > Thanks. >=20 > - Trevor >=20 >=20 >=20 > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.572 / Virus Database: 362 - Release Date: 1/27/2004 >=20 >=20 > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to digest@talk.smithmicro.com> > Web Archive of this list is at: http://webdna.smithmicro.com/ >=20 > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to digest@talk.smithmicro.com> > Web Archive of this list is at: http://webdna.smithmicro.com/ >=20 > --- > Incoming mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.572 / Virus Database: 362 - Release Date: 1/27/2004 >=20 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.572 / Virus Database: 362 - Release Date: 1/27/2004 =20 ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ "Crist, Trevor"

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

Claris HomePage messes up the code (1997) cart info (1998) F3 crashing server (1997) [url] issue (2000) RE: [WebDNA] An unknown error occured // Deadlock avoided (2011) multiple price line in formula.db (2004) Sorting Orders (1997) Database Helper missing? (2000) [isfile] ? (1997) Using Plug-In while running 1.6.1 (1997) WC2.0 Memory Requirements (1997) Webstar 1.3.1 PPC (1997) expired beta (1997) auction system w/ Web Cat (1999) Version 4? (2000) Problem with summary on date / inconsequent webcat behaviour (1998) What is the maximum record length? (1998) PCS Frames (1997) no? marks in the links (2003) Blocking off access (2005)