Shapefiles are only marginally part of the geodatabase model, mostly because they don't conform to the full range of datatypes and NULL support (not to mention the field naming limitations and byte-sized length limit).
Geodatabase, the model, doesn't have limits. File geodatabase, the format, doesn't have limits*. Enterprise geodatabase, the format, only has what limits are imposed by the RDBMS vendor. Admittedly, juggling between these formats can be a PITA, but that's not a limitation of geodatabase.
I'm also mystified by the resurrection.
- V
* Where 2Gb-1 is "effectively unlimited"
Thanks Vince... I will stick with multidimensional arrays... life is much simpler