: 4582 | 108584 | 12352

XPages: @DBLookupBig & @DbColumnBig 
New idea submissions, commenting and voting are no longer available on this site. Logins have also been disabled.
Use this IdeaSpace to post ideas about Domino Designer.

: 32
: 33
: 1
: Domino Designer
: formula, xpages, @Dblookup, @DBcolumn
: Erik Brooks795 11 Oct 2009
:
: / Email
XPages are here, they're big and bad and scalable. They integrate with @Formulas, which is extremely powerful. For things like repeat controls, type-ahead, etc. there are times when you use @DbLookup or @DbColumn.
 
But these functions are limited in returning 64K, like the days of old.
 
Two new @Formulas, @DbColumnBig and @DbLookupBig should be created to be able to return large amounts of data.
 
Presumably to incorporate this capability into the legacy design elements (<computed text>, fields, etc.) this would be a large amount of effort because of all the other 16/32/64K limits on those elements.  To ease the engineering effort on IBM's side the new @Formulas could be made available only within the context of XPages, similar to how @Unique has a completely different implementation on XPages than it does with legacy Domino design elements.
 



1) Rob Goudvis6585 (12 Oct 2009)
Why should there be a special @formula for this. Why not allow for more data to be returned in the existing @formulae? You could think of a new optional parameter that could limit your return size (like NotesDatabase.Search).
2) Oliver Regelmann4949 (14 Oct 2009)
I agree with Rob. The original formulas should get enabled to return more data.
3) Erik Brooks795 (21 Oct 2009)
@1 & @2 - I thought I answered that? If you changed @DbColumn to return more data you'd potentially break all of the other design elements out there. At the very least they'd all be returning different error messages on large sets ("Formula is too large" instead of "@DbColumn returned more than 64K of data").

If they could rework the existing formulas, that'd be great. But what would likely be easier for IBM from an engineering and backwards-compatibility standpoint would be to add the new ones and surface those in the places (e.g. XPages) where they would work.

Or they could simply change @DbLookup / @DbColumn to "@V8DbLookup" and "@V8DbColumn" like they've done with other deprecated @Formulas.
4) Tommy Valand2746 (09 Feb 2011)
A little late to the party. I agree with the first two. In XPages, there's no 64k limit on components that I'm aware of, so there's no danger of destroying existing XPages applications if the "limit" was removed.

In formula, I would rather have a parameter for the limit, than having a new command to deal with.

e.g. [ReturnAll] or [NoLimit] (there's probably a better name)










:
:




Welcome to IdeaJam™


You can run IdeaJam™ in your company. It's easy to install, setup and customize. Your employees, partners and customers will immediately see results.

Use IdeaJam to:

  • Collect ideas from employees
  • Solicit feedback and suggestions from employees and customers
  • Run innovation contests and competitions
  • Validate concepts
  • Use the power of "crowd-sourcing" to rank ideas and allow the best ideas to rise to the top

IdeaJam™ works with:

  • IBM Connections
  • IBM Lotus Quickr
  • Blogs and Wikis
  • Websphere Portal
  • Microsoft Sharepoint
  • and other applications.

IdeaJam has an extensive set of widgets and API's that allow you to extend and integrate IdeaJam™ with other applications.

Learn more about IdeaJam >>






IdeaJam developed by

Elguji Software Logo