Re: dbexport problem

Cats wrote: > Ben, not sure how your theory squares with my now having managed to > export two databases containing tigs.ref. My own theory now is a > transient disk problem. I strongly disagree. We have had exactly the same problem with a column called 'ref' in our databases which we had five separate tables. All tables exhibited the problem and call could be fixed with the workaround I suggested. The same database design exists on many servers at our customers and many, if not all of them, at one time exhibited the problem. I think you're right to say that the problem is dependent on a number of variables which may be when the column was created, with which version, and what version you're using now. I generally don't use IDS7 very much any more and I can't even reproduce it the one instance I have left which runs 7.31.UD4. We used to use 7.31.UC5/6 and 7.31.TC5 a lot and these versions most certainly had the problem. What I am certain of, however, is that this is a bug in IDS and nothing whatsoever to do with your discs. Regards, Ben.

Ben Thompson wrote: > Cats wrote: > >> Ben, not sure how your theory squares with my now having managed to >> export two databases containing tigs.ref. My own theory now is a >> transient disk problem. > > I strongly disagree. We have had exactly the same problem with a column > called 'ref' in our databases which we had five separate tables. All > tables exhibited the problem and call could be fixed with the workaround > I suggested. The same database design exists on many servers at our > customers and many, if not all of them, at one time exhibited the problem. > > I think you're right to say that the problem is dependent on a number of > variables which may be when the column was created, with which version, > and what version you're using now. I generally don't use IDS7 very much > any more and I can't even reproduce it the one instance I have left > which runs 7.31.UD4. We used to use 7.31.UC5/6 and 7.31.TC5 a lot and > these versions most certainly had the problem. > > What I am certain of, however, is that this is a bug in IDS and nothing > whatsoever to do with your discs. > > Regards, Ben. REF has been a SQL reserved word since IDS 9.20 Although you can use almost any word as an SQL identifier, syntactic ambiguities might occur if you use an SQL reserved word. An ambiguous statement might not produce the results you want. REFerence type is part of the ISO SQL standard.