Re: Reserved words - Enhancement request
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 28453
interpreted = N
texte = I am getting so very tired of always agreeing with Ken and being awed by his brilliance. Knock it off Ken :)Hey SM! What he said!! I am so sick of *ucking legacy code hassles in everything. Make it **RIGHT**Right now we are in the middle of specking out a huge mls project, and about half of the isp's involved want to make it so the 'new' system works with their old setup. Now, keep in mind that this is a database with 'date' field, which is exactly the same in every record, with 27,000 entries of the date the data was compiled, which incidentally, is also the lastmod date of the database. But the 'date' the listing was added isn't in the database.-Aaron > Nothing will break sites developed for 3.x versions unless the > user upgrades, and there's no reason why anyone would HAVE TO > upgrade to a newer version. This is not a communist country and > we are not forced to upgrade -- we will *always* have a choice of > whether to upgrade or not. > > Saying it's too late is just an excuse, because it is NEVER too > late to fix problems. Any prudent software firm will fix every > bug or problematic feature it is aware of -- if it actually hopes > to make its software the best possible product in the long run ... > > Any site that currently runs webcatalog 3.x will continue to work > fine while running version 3.x, so to ignore this fix at the > expense of everyone who might end up buying webcatalog in the > future is a decision based not on the future quality of the > product, but on other parameters such as whatever is 'easiest' or > 'cheapest' thing to do ... > > It takes real pride in your product to 'bite the bullet' and fix > things that should have been fixed a long time ago, especially > when the fixing might make more work for you and cost your > company some money in the short term. IT seems to me that the > most successful companies all over the world tend to fix things > when their users inform them of problems, especially when those > same users care enough to spend their time describing the > problems and suggesting potential solutions. > > What's more, I see no reason why a new version with this stuff > fixed cannot be run on the same server that already has an older > version of webcatalog running on it -- provided SM recognizes the > need of some users to continue using an old version concurrently > with a new version on the same box. > > >There IS something we can do now AND something that SM could do to > >ease the pain. > > > >We as users should start coding all db field names with a 2 character > >prefix. dbPrice or myPrice would solve the problem. > > No this will not solve the problem. The shopping cart code built > into in webcatalog *requires* a price field in the database, > and it also references a price field in the cart file. These > field names are non-negotiable, and there will continue to be > problems whenever a [price] tag is used inside a founditems > context which appears inside or around an orderfile context -- > unless work-arounds are implemented. > > ================================ > Kenneth Grome, WebDNA Consultant > 808-737-6499 http://webdna.net > ================================ > > ------------------------------------------------------------- > Brought to you by CommuniGate Pro - The Buzz Word Compliant > Messaging Server. > To end your Mail problems go to
. > > 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 > > ------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go to .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
Associated Messages, from the most recent to the oldest:
I am getting so very tired of always agreeing with Ken and being awed by his brilliance. Knock it off Ken :)Hey SM! What he said!! I am so sick of *ucking legacy code hassles in everything. Make it **RIGHT**Right now we are in the middle of specking out a huge mls project, and about half of the isp's involved want to make it so the 'new' system works with their old setup. Now, keep in mind that this is a database with 'date' field, which is exactly the same in every record, with 27,000 entries of the date the data was compiled, which incidentally, is also the lastmod date of the database. But the 'date' the listing was added isn't in the database.-Aaron > Nothing will break sites developed for 3.x versions unless the > user upgrades, and there's no reason why anyone would HAVE TO > upgrade to a newer version. This is not a communist country and > we are not forced to upgrade -- we will *always* have a choice of > whether to upgrade or not. > > Saying it's too late is just an excuse, because it is NEVER too > late to fix problems. Any prudent software firm will fix every > bug or problematic feature it is aware of -- if it actually hopes > to make its software the best possible product in the long run ... > > Any site that currently runs webcatalog 3.x will continue to work > fine while running version 3.x, so to ignore this fix at the > expense of everyone who might end up buying webcatalog in the > future is a decision based not on the future quality of the > product, but on other parameters such as whatever is 'easiest' or > 'cheapest' thing to do ... > > It takes real pride in your product to 'bite the bullet' and fix > things that should have been fixed a long time ago, especially > when the fixing might make more work for you and cost your > company some money in the short term. IT seems to me that the > most successful companies all over the world tend to fix things > when their users inform them of problems, especially when those > same users care enough to spend their time describing the > problems and suggesting potential solutions. > > What's more, I see no reason why a new version with this stuff > fixed cannot be run on the same server that already has an older > version of webcatalog running on it -- provided SM recognizes the > need of some users to continue using an old version concurrently > with a new version on the same box. > > >There IS something we can do now AND something that SM could do to > >ease the pain. > > > >We as users should start coding all db field names with a 2 character > >prefix. dbPrice or myPrice would solve the problem. > > No this will not solve the problem. The shopping cart code built > into in webcatalog *requires* a price field in the database, > and it also references a price field in the cart file. These > field names are non-negotiable, and there will continue to be > problems whenever a [price] tag is used inside a founditems > context which appears inside or around an orderfile context -- > unless work-arounds are implemented. > > ================================ > Kenneth Grome, WebDNA Consultant > 808-737-6499 http://webdna.net > ================================ > > ------------------------------------------------------------- > Brought to you by CommuniGate Pro - The Buzz Word Compliant > Messaging Server. > To end your Mail problems go to . > > 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 > > ------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go to .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
Aaron Lynch
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:
Cookie setting (2003)
instant cookies? (1999)
Problems passing [SKU] with $Replace in 2.0 (1997)
auction site (2000)
HELP WITH DATES (1997)
Late on Friday.... brain fried (2002)
Stupid question (2003)
Postdata expired from cache (2004)
email preferences on NT (1997)
[SHOWNEXT] Examples (1997)
Help! WebCat2 bug (1997)
Converting Quotes in Javascript (2001)
Using WebCat for product info requests (1997)
Searching multiple Databases (1997)
Fun with dates (1997)
Permissions Ignored - PLEASE HELP (2003)
Blocking off access (2005)
[INCLUDE] Limitations (1998)
Pithy questions on webcommerce & siteedit (1997)
Referrer field to header field conversion (1997)