Zugg Software :: View topic - Feature suggestion: More database record functions

Wizard Joined: 14 Aug 2004 Posts: 1269

I did look at your last post when you wrote it (which was after I started this thread), but I didn't really analyse it, I have to admit, as it still looked fairly horrible (or even more horrible than the previous version). My original point here was that there should really be easier and more efficient ways of doing these things, and that some extra database record functions might help in many cases. Taking a closer look at your last post in that thread now, it doesn't look like it would run terribly fast on a sizable database record variable, but maybe #LOOPDB is very fast?

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

Loopdb is fairly fast. That wasn't the point though. Or at least not why I spoke up. Zugg's new functions pretty much do the work of the loopdb.

My point was that the %expanddb(@var) really wasn't the way that it should be handled in this case.

What Zugg mentioned about using the functions inside the trigger pattern being pretty much undefined is what made me think I needed to delete and recreate the trigger each time.

Then I thought of the much more reasonable method that I mentioned above. Just creating a list variable from the database variable.

SubAdmin Joined: 18 Nov 2001 Posts: 5187

Gentlemen,

I think this topic has seen enough debate back and forth. Zugg found the time to add some wonderful new features amidst all the bug fixing and I don't think arguements about it are going to help anything. Please take a few moments to breathe and consider whether further debate is needed.

Wizard Joined: 14 Aug 2004 Posts: 1269

Who's arguing? I'm sorry if I came off as arguing, but that's not it at all. I thought I summarized the point of this thread quite succinctly in my last post and didn't feel any further debate was needed. If we have even had any debate here. I think this thread would have died if you hadn't posted! Wink