Re: [WebDNA] No more SQL in 7.1?
This WebDNA talk-list message is from 2012
It keeps the original formatting.
numero = 108490
interpreted = N
texte = aaronmichaelmusic@gmail.com wrote: > Will SQL syntax be totally gone in 7.1? My .0001=A2 I appreciate Chris that you are trying to make the language easy to=20 install.. and perhaps more to the point, easier for you to keep up=20 development for WebDNA. Perhaps I need to take that into account before=20 I make reaction posts to a public list. So, let me be serious... It has been said publicly (so it is no secret) that WSC is on a tight=20 budget right now, and yes, perhaps getting rid of more libraries will=20 make it easier to handle. I want to say on a positive note that it sounded like you are keeping=20 xalan and xerces (XML contexts/tags) now, which is good news! Things like SOAP, AJAX (Usually JSON or XML for the vehicle), XML,=20 RDBMS's (MySQL and others), and the DOM are not going to go away and for=20 developers like myself, who make their living working on a wide array of=20 projects for clients, don't like to see WebDNA lose support for the=20 main-stays of the industry. I have seen countless times where WebDNA has=20 fallen from usage from a company because it didn't talk right with other=20 technologies. For a language to be attractive, it has to contain certain=20 standards. At the least, a lack of them will prompt bad reviews if/when=20 WebDNA was ever to gain any footing at all again. I also don't like to=20 see a loss of support for good traditional qualities of WebDNA, such as=20 the commerce tags/contexts. Contrary to some of you all's belief, the=20 commerce tags are still really helpful and useful... not just for=20 commerce, but for "sessioning" as well.. they are not that much=20 different than PHP's $_SESSION system. Yes, you can build a session in=20 PHP as well from scratch.. but it doesn't mean that's always the best=20 choice ;-) My suggestion (and plea) for WebDNA's future, is for Chris to consider=20 taking on more help from others, whom may want to offer it. Trying to do=20 this all on your own is an effort in futility. If you get others=20 involved, you'll be able to support the product easier. Just getting rid of the things that are "hard to deal with" for you is=20 not the answer. Our industry, and working with *any* programming=20 language is, at it's root, complicated. Striving for simplicity is=20 great, but sacrificing standards (SOAP, XSLT, XML, SESSIONS, RDBMS's=20 (MySQL PostGreSQL), JSON, etc.. is not the answer) Now, I know you.. you are going to do what you want in the end, and you=20 will respond with your reasoning... but for yours and WebDNA's sake, I=20 hope that something I said here sinks in. For those of you whom are newer: - Commerce Tags do not equal commands - SQL is different from MySQL.. and so to are the tags/contexts of WebDNA. ([SQL..] is very very old, slow, and outdated API for ODBC and=20 it has little to do with MySQL... it was on my list to change the name=20 of that context to [ODBC..] and deprecate [SQL..]) Anyway, yes, I love WebDNA's innate database (even if Grant doesn't ;-)=20 ), but seriously.. get more people involved, and keep up support for=20 standards. Donovan (off to an RV and Camper show!) :-) Happy Friday! --=20 Donovan Brooke Euca Design Center www.euca.us
Associated Messages, from the most recent to the oldest:
aaronmichaelmusic@gmail.com wrote: > Will SQL syntax be totally gone in 7.1? My .0001=A2 I appreciate Chris that you are trying to make the language easy to=20 install.. and perhaps more to the point, easier for you to keep up=20 development for WebDNA. Perhaps I need to take that into account before=20 I make reaction posts to a public list. So, let me be serious... It has been said publicly (so it is no secret) that WSC is on a tight=20 budget right now, and yes, perhaps getting rid of more libraries will=20 make it easier to handle. I want to say on a positive note that it sounded like you are keeping=20 xalan and xerces (XML contexts/tags) now, which is good news! Things like SOAP, AJAX (Usually JSON or XML for the vehicle), XML,=20 RDBMS's (MySQL and others), and the DOM are not going to go away and for=20 developers like myself, who make their living working on a wide array of=20 projects for clients, don't like to see WebDNA lose support for the=20 main-stays of the industry. I have seen countless times where WebDNA has=20 fallen from usage from a company because it didn't talk right with other=20 technologies. For a language to be attractive, it has to contain certain=20 standards. At the least, a lack of them will prompt bad reviews if/when=20 WebDNA was ever to gain any footing at all again. I also don't like to=20 see a loss of support for good traditional qualities of WebDNA, such as=20 the commerce tags/contexts. Contrary to some of you all's belief, the=20 commerce tags are still really helpful and useful... not just for=20 commerce, but for "sessioning" as well.. they are not that much=20 different than PHP's $_SESSION system. Yes, you can build a session in=20 PHP as well from scratch.. but it doesn't mean that's always the best=20 choice ;-) My suggestion (and plea) for WebDNA's future, is for Chris to consider=20 taking on more help from others, whom may want to offer it. Trying to do=20 this all on your own is an effort in futility. If you get others=20 involved, you'll be able to support the product easier. Just getting rid of the things that are "hard to deal with" for you is=20 not the answer. Our industry, and working with *any* programming=20 language is, at it's root, complicated. Striving for simplicity is=20 great, but sacrificing standards (SOAP, XSLT, XML, SESSIONS, RDBMS's=20 (MySQL PostGreSQL), JSON, etc.. is not the answer) Now, I know you.. you are going to do what you want in the end, and you=20 will respond with your reasoning... but for yours and WebDNA's sake, I=20 hope that something I said here sinks in. For those of you whom are newer: - Commerce Tags do not equal commands - SQL is different from MySQL.. and so to are the tags/contexts of WebDNA. ([SQL..] is very very old, slow, and outdated API for
ODBC and=20 it has little to do with MySQL... it was on my list to change the name=20 of that context to [
ODBC..] and deprecate [SQL..]) Anyway, yes, I love WebDNA's innate database (even if Grant doesn't ;-)=20 ), but seriously.. get more people involved, and keep up support for=20 standards. Donovan (off to an RV and Camper show!) :-) Happy Friday! --=20 Donovan Brooke Euca Design Center www.euca.us
Donovan Brooke
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:
authorizenet and netscape (2002)
Ok here is a question? (1997)
Emailer not working (1998)
triggers (2003)
Cart Creation (1998)
Anyone awake? Newby moves deeper! Sitesearch & (2000)
New Mac Emailer... (1997)
command parameters (1998)
Emailer errors & disappearing messages (1998)
How to search dbs across virtual hosts for same domain? (2003)
emailer (1997)
[Announce]: Web server security and password protection (1997)
HELP WITH DATES (1997)
DataBaseHelper Flawed (1997)
WebCat cannot handle compatible search parameters? (1997)
Colors in cart (2002)
Sandbox scripts (2004)
WC2b15 - [HTMLx]...[/HTMLx] problems (1997)
Understanding texta (1997)
grep is really pathetic sometimes (2003)