Most often we don't really know if customers rely on a particular behavior in
the product.
When UniData has behaved in a particular manner for many years, we hesitate to
just change the behavior in some cases. We have been surprised more than once
when we did change behavior without providing
Will
I don't understand what's wrong with indexing, can you clarify this point,
and I'll wipe out a fix in three days :)
Well for a start I didn't say there's anything wrong, I said it could be
improved - not the same thing!
But as to specifics, take the following scenario (UniVerse specific):
Will and Brian,
I had a similar experience. I indexed a file that had over a million records
with the same code. All was ok for a couple of hours and then Universe crashed
with something like out of string space.
It was ugly!
Had this worked, it would have been a great benefit but .
The first part is relatively trivial for a person of my level of genius :)
The second part is so utterly Byzantine and unfathomable (and redundant
apparently) that I would never even make the attempt. What Rocket adopts and
also what they discard, has never been comprehendable.
So there you
Hi,
If I understand correctly, you're asking how the data embedded in the xml gets
parsed out and written to a uv file, correct? If so, we use a uv function
called XMLTODB, it's in the bp of the uv account.
We accept orders from college book stores and we do that by consuming their web
Brian:
I was under the impression that UniData uses a real B-Tree indexing
system while UniVerse uses some kind of linked list. e.g. UV has a
single item for, say, male/female and the item would look like
ID: male
001 1]2]3]4]5]6]...]999
...which would perform exactly as you say. I
Bill
I *did* say UniVerse specific :)
Yes, it uses a really nice and well-designed B+Tree for the index keys but
once you're down to the data (the primary keys) they are stored in a regular
record format with @FM between each key. You can see that easily enough as
you can create a pointer to the
Gives you a sort of Dilbert like impression that at the end of the project,
once all the B tree bugs were worked out, they were shouting Just make it
work, we'll make it better next version!
Only next version never came.
Yes Brian a B-tree on a B-tree probably makes the most sense from a
Ah, makes sense. Thanks!
On Fri, Oct 5, 2012 at 6:20 AM, Wally Terhune
wterh...@rocketsoftware.comwrote:
Most often we don't really know if customers rely on a particular behavior
in the product.
When UniData has behaved in a particular manner for many years, we
hesitate to just change the
I have talked to programmers at conferences and places like that, and
some of them have utilitized techniques like that to ensure that their
bills are paid on time...(smile)...
Robert Norman
On 10/4/2012 7:18 PM, Kevin King wrote:
I just found this in the UDT.OPTIONS manual...
If
I have talked to programmers at conferences and places like that, and
some of them have utilized techniques like that to ensure that their
bills are paid on time...(smile)...
Robert Norman
On 10/4/2012 7:18 PM, Kevin King wrote:
I just found this in the UDT.OPTIONS manual...
If UDT.OPTIONS
11 matches
Mail list logo
