Re: WARNING:Latest 4GL+Online buggy
OK, let's sort this out once & for all. As far as I can tell, the techinfo David is referring to is TECH ALERT: 2-digit yr-dts in expressions misinterpreted this is due to the fact that as it stands when it comes to triggers expression evaluation, fragmentation expression evaluation, or stored procedures we use the current session dbcentury settings, as opposed to the dbcentury settings of the session that created the fragmented table, the trigger or the stored procedure. Note that this has always been the case, and is not something that has popped out in 7.31.xCx. There has been a request by which this behaviour should be changed, and this is going to be implemented in 7.31.UC4. Now please let me be clear about this, DBCENTURY is a feature designed to simplify application user's life - there is *no excuse* for using 2 digits for years in date constants in DDL statements & SPL. As for 4gl 7.30, it appears that after a prepare, the contents of char variable containing the statement to be prepared are modified. I haven't had a chance to have a look at the case opened by Dave, so I can't comment on this. BTW Ali - somebody is looking for the source code of a financial package written in 4gl. I'm sure you can find a way of placing another of your plugs, here! -- Ciao, Marco ______________________________________________________________________________ Marco Greco <marco@informix.com> Standard disclaimers apply! Informix faq http://www.iiug.org/techinfo/faq/informix.htm 4glworks http://www.ctonline.it/~marcog Informix on Linux http://www.ctonline.it/~marcog/ifmxlinux.htm
In article <380C5494.55B2BD5E@informix.com>, Marco Greco <marco@informix.com> writes >OK, let's sort this out once & for all. >As far as I can tell, the techinfo David is referring to is > >TECH ALERT: 2-digit yr-dts in expressions misinterpreted > >this is due to the fact that as it stands when it comes to triggers expression >evaluation, fragmentation expression evaluation, or stored procedures we use >the current session dbcentury settings, as opposed to the dbcentury settings of >the session that created the fragmented table, the trigger or the stored >procedure. >Note that this has always been the case, and is not something that has popped >out in 7.31.xCx. There has been a request by which this behaviour should be >changed, and this is going to be implemented in 7.31.UC4. >Now please let me be clear about this, DBCENTURY is a feature designed to >simplify application user's life - there is *no excuse* for using 2 digits for >years in date constants in DDL statements & SPL. > Agreed, but y2k has a fixed deadline and not everyone will have time to check every line of DDL. We should be able to set it to "C" and not worrying since our systems handle dates from TODAY onwards, hence we know that using the closest century wiil work everywhere. This makes our systems more reliable since even reading code and testing will not catch everything! >As for 4gl 7.30, it appears that after a prepare, the contents of char variable >containing the statement to be prepared are modified. I haven't had a chance to >have a look at the case opened by Dave, so I can't comment on this. > OK, but I though people should be aware of this so they don't go live with it and find problems later or waste time installing and testing it. I'm not trying to have a go at UK Tech Support, you guys have always been the best and I want to commend people there for the support we get. I moved jobs to stay with Informix rather then move to O***le and I've paided over 2000 quid our of my own pocket for training courses at Informix offices in Sunbury. I'm perfectly happy with the level of support, I couldn't really ask more from you.. I was wondering if anyone else in c.d.i. had logged a case anywhere since we can link the cases together. UK Tech Support tends to be behind the US in the version they have since obviously the US/Menlo Park will get versions first. I'd like to co-ordinate efforts and link cases to others if I can. Maybe we can even help save some of Informix's time duplicating effort! Perhaps someone in the States may be the first to find a fix??? Sorry if my initial post sounded nasty I panicked , so many sites to upgrade, so little time!! HELP!!!! ARRGH! >BTW Ali - somebody is looking for the source code of a financial package >written in 4gl. I'm sure you can find a way of placing another of your plugs, >here! :->>>> -- David Williams
David Williams wrote: > > In article <380C5494.55B2BD5E@informix.com>, Marco Greco > <marco@informix.com> writes > >OK, let's sort this out once & for all. > >As far as I can tell, the techinfo David is referring to is > > > >TECH ALERT: 2-digit yr-dts in expressions misinterpreted > > > >this is due to the fact that as it stands when it comes to triggers expression > >evaluation, fragmentation expression evaluation, or stored procedures we use > >the current session dbcentury settings, as opposed to the dbcentury settings of > >the session that created the fragmented table, the trigger or the stored > >procedure. > >Note that this has always been the case, and is not something that has popped > >out in 7.31.xCx. There has been a request by which this behaviour should be > >changed, and this is going to be implemented in 7.31.UC4. > >Now please let me be clear about this, DBCENTURY is a feature designed to > >simplify application user's life - there is *no excuse* for using 2 digits for > >years in date constants in DDL statements & SPL. > > > Agreed, but y2k has a fixed deadline and not everyone will have time > to check every line of DDL. > > We should be able to set it to "C" and not worrying since our systems > handle dates from TODAY onwards, hence we know that using the closest > century wiil work everywhere. This makes our systems more reliable > since even reading code and testing will not catch everything! FYI Informix has a utility, CheckDates, that will go through the ALL of your system tables, triggers, views, and SPL and detect ANY 2digit years that you may have used in DDL to create triggers, views, procedures, or fragmentation expressions so you can correct these before January. Contact Informix support to get a copy. This is distributes as a package with executables for several platforms which can be run remotely if you have a non-supported platform. Art S. Kagel