Search results

We use RTB, but we don't really use it for deployment per se - really it's just for versioning. Our deployment system is an unbelievably complicated organically developed collection of tools written in various languages by many people over many years, and we have 5 (or so) full-time people...

OK, after looking a bit more closely, I have to more-or-less concede this one. It's actually picking the *last* one (that starts with 't'), which happens to be the _only_ table we have that starts with a unique combination of the first two letters. Eg. all our 'a' tables start with 'ac', etc...

On my system (10.2B05) and with a more realistic DB (eg. not Sports), 't' seems to be special... we have dozens of tables that start with 't' and dozens that start with 'a' ... 't' has this behaviour, other letters including 'a' do not. -- 100% agreed about abbreviations and unqualified field...

Hmm, seems like almost nobody shares my fascination for this weird corner of Progressdom. Anyway, it turns out that this same issue affects everything, eg: find first t. disp t. ... or ... def temp-table whatever like t. These work, too, even if the DB doesn't have a table named 't' in...

I'm not looking for a solution, I just thought some of the Progress old-timers like me might appreciate this. Connect to sports2000 (it doesn't happen with sports or isports for semi-obvious reasons) and run this code. Yeah, I know it's not proper code, that's not important. And sorry about the...

Is this a question or just a statement of fact? Anyhow ... my guess is, some other process is, in some way, writing to the file at the same time.

Not my area, but, I do not normally see multiple ubroker.properties files on a single machine. As far as I know, you just can't do that, you'd have to use different servers. We have VM's everywhere so for us this is no big deal. Exception: we have a few machines with multiple Progress...

I'm not familiar with SpeedScript, but would this work? def temp-table t no-undo field f as char. def var h as handle no-undo. h = temp-table t:handle. disp can-query(h,"WRITE-JSON"). The temp-table is here only so I can query its WRITE-JSON method. It's not actually doing anything. If this...

Oops! Not quite. The 'put stream x', DUH, is just referencing the procedure-visible stream defined previously. A good example of why I'd like a 'make procedure-level names invisible inside internal procedures' compiler option. Anyway. I don't have a compiler in front of me, but it's probably...

For the record, this seems to work and seems to meet the original requirement: def stream x. output stream x to /tmp/gt1. run p(stream x:handle). output stream x close. output stream x to /tmp/gt2. run p(stream x:handle). output stream x close. procedure p: def input param s as handle. /*...

Here's a suggestion that might be totally useless: if you, say, suspect a lot of reads on the FOO table, you could add a session trigger to the top of the call stack 'on read of FOO'. Then in the trigger, you could log the details of the access. I'm not sure how much detail you can get (eg. you...

I kind of glossed over the OP's comment about -rereadnolock. That might be important. We always use -rereadnolock (I think) and in any case I was trying this from a simple self-service client. I'm fuzzy on how VST's and remote clients interrelate. Details, details. TIL about _UserTableStat, aha...

If you 'find first x' inside a loop of 10, the VST _tablestat-read number will increase by 10. I just verified this quickly. The fact that 9 of those reads were most likely from memory doesn't seem to matter. A flaw with this, however, is that _tablestat is across all users. I'm not aware of a...

If you could find the grammar definition from a current version (these definitely exist though I don't personally know where), you could feed that into the KEYWORD function. This would be relying on Progress never removing keywords, which as far as I know, is true ;) OR, you could write a...

There is a startup parameter eg. '-rg' that you can use to alter the type of Progress session for specific users (eg. give a user lower capability than the Progress installation otherwise allows). Perhaps your account is using this and everyone else is not...

I'm not sure what you mean by "check" or whether you're talking about the RUN statement or the DEF INPUT PARAM side of things. However, bottom line, AFAIK (I'm not up on recent releases as we don't use them): - you can use GET-SIGNATURE to discover parameters of internal procedures - FUNCTION...

The OP didn't suggest that Procedure1/Procedure2 does a particularly huge amount of work, did he? I don't see problem with that code, assuming that he's not updating thousands of records. IMO there is nothing necessarily wrong with splitting logic up as his code suggests. Regardless, what I...

We never use async requests, we have a whole different approach, but here are 2 thoughts: 1) Possibly hProcess should be an array indexed by 'i', so that you can track each request handle and figure out what to do in endasync; 2) Back when we contemplated using async requests, someone alleged...

I think he means he wants to search all the (character, presumably) columns in all the tables, for a particular value, without naming each table and field in the query. Like this: http://stackoverflow.com/questions/8815025/apply-like-over-all-columns-without-specifying-all-column-names It...

Your code is a little too involved for me to be motivated to recreate it, but the only thing that stands out to me is that we don't normally use (a) multiple targets in an ON (ON PF4, ENDKEY), nor (b) the same key in multiple ON statements (ON PF4 twice). Both may be OK, I'm not sure, but it...