Re: WebDNA Feature Request
This WebDNA talk-list message is from 2006
It keeps the original formatting.
numero = 67784
interpreted = N
texte = On 7/10/06 4:05 PM, "John Peacock"
wrote: > Nitai @ ComputerOil wrote: >> 1. Major Database support build in. Connect natively to Oracle, DB2, MS SQL. > > WebDNA already has ODBC support. What are you expecting native drivers > to cost to develop? Here's a hint: it's really hard to bind to multiple > databases with native drivers; you wind up building an abstraction layer > which winds up just duplicating ODBC (as pathetic as *that* is). It's a > big distraction from features that everyone will use. It may be but native MSSQL support is something that has 'supposedly' been on the list for a very long time. This is exceptionally important to us since discovering that the ODBC support from OSX to MSSQL is FAR from stable. We have it working but are still working around various error issues. >> As long as we can't connect to other systems, WebDNA can not compete >> with other systems. Flat file is nice and fast, but you can't argue with >> a CEO and lack of SQL support. > > Sure I can. All I have to do is point out the cost of Oracle (per CPU > or per seat) or MS SQL (per connection plus per server?). Your > licensing cost depends on your traffic, whereas right now your licensing > is flat with regards to traffic. If you already have an enterprise SQL > solution, you already have staff to support the database (which is not > something that HTML jockeys should attempt). But, an experienced Oracle > DBA is $120k per year in my market, so a free database usually beats out > a commercial one for most purposes. Again, it depends on your clientele and projects. Most of our jobs now are working with MSSQL (windows server) with WebDNA as just one of the front ends. The SQL data is being manipulated from various other front ends and the ability to for DNA to integrate into that workflow was the ONLY reason we were able to get it in there. Unfortunately without the native support for MSSQL which has been "coming soon" for almost 2 years, we are dependant on ODBC and the issues that brings with platform variations. Trust me, if the ODBC was stable and didn't offer any performance degradation I would rather stay there because the sql syntax is identical as it is pretty much just passed as a string. But when you get into complex error returns and unexpected binary data in your dataset you realize how important the native support would be. This feature is the thee most important item we have been waiting for (as we were led to believe) for some time. I am hoping to see some type of direction list from SMSI to help guide the movement forward before it derails into a collage of feature request hodgepodge. Just my .02 -- Alex McCombie .. . . . . . . . . . . . . . . . . . . . . . . . . . . . Adventure Skies Interactive Box 124 Martville, NY 131111 p. 315 .233 .9403 e. Alex@AdventureSkies.com http://AdventureSkies.com ------------------------------------------------------------- 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:
On 7/10/06 4:05 PM, "John Peacock" wrote: > Nitai @ ComputerOil wrote: >> 1. Major Database support build in. Connect natively to Oracle, DB2, MS SQL. > > WebDNA already has ODBC support. What are you expecting native drivers > to cost to develop? Here's a hint: it's really hard to bind to multiple > databases with native drivers; you wind up building an abstraction layer > which winds up just duplicating ODBC (as pathetic as *that* is). It's a > big distraction from features that everyone will use. It may be but native MSSQL support is something that has 'supposedly' been on the list for a very long time. This is exceptionally important to us since discovering that the ODBC support from OSX to MSSQL is FAR from stable. We have it working but are still working around various error issues. >> As long as we can't connect to other systems, WebDNA can not compete >> with other systems. Flat file is nice and fast, but you can't argue with >> a CEO and lack of SQL support. > > Sure I can. All I have to do is point out the cost of Oracle (per CPU > or per seat) or MS SQL (per connection plus per server?). Your > licensing cost depends on your traffic, whereas right now your licensing > is flat with regards to traffic. If you already have an enterprise SQL > solution, you already have staff to support the database (which is not > something that HTML jockeys should attempt). But, an experienced Oracle > DBA is $120k per year in my market, so a free database usually beats out > a commercial one for most purposes. Again, it depends on your clientele and projects. Most of our jobs now are working with MSSQL (windows server) with WebDNA as just one of the front ends. The SQL data is being manipulated from various other front ends and the ability to for DNA to integrate into that workflow was the ONLY reason we were able to get it in there. Unfortunately without the native support for MSSQL which has been "coming soon" for almost 2 years, we are dependant on ODBC and the issues that brings with platform variations. Trust me, if the ODBC was stable and didn't offer any performance degradation I would rather stay there because the sql syntax is identical as it is pretty much just passed as a string. But when you get into complex error returns and unexpected binary data in your dataset you realize how important the native support would be. This feature is the thee most important item we have been waiting for (as we were led to believe) for some time. I am hoping to see some type of direction list from SMSI to help guide the movement forward before it derails into a collage of feature request hodgepodge. Just my .02 -- Alex McCombie .. . . . . . . . . . . . . . . . . . . . . . . . . . . . Adventure Skies Interactive Box 124 Martville, NY 131111 p. 315 .233 .9403 e. Alex@AdventureSkies.com http://AdventureSkies.com ------------------------------------------------------------- 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/
Alex McCombie
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:
Mac: [ListFiles] bug alert (1997)
Multiple Ad databases? (1997)
New WebCatalog Version !!! (1997)
Plaintext Email Attachment (2001)
New to WebCat, Help. (1998)
Form/HTML Help (2000)
Is there an alternative to emailer? (1999)
NY taxRates.db? (1997)
Digital Postcards (1999)
Time/date formatting %X doesn't work ... (1997)
[format] problem (2001)
[WebDNA] Some JS help please (2010)
Adding Header Values with [SetHeader] (1998)
Close-to Comparison Code (1998)
Sorting error (1997)
Lookup command (1998)
webcat- multiple selection in input field (1997)
[OT] On a side note.. (2003)
Webcatalog quitting (1997)
Closing Databases (1998)