A vote of confidence.

[Rophicus]

To the pro-active contributors of this group:

To date I've mostly been standing on the sidelines as a lurker. I've
scanned the code a bit, looked at the doc and Wiki, and especially
watched the ongoing group discussions with great interest.
Regretfully I'm not yet at the point of work on my project to be
actively using, and therefore also proactively contributing to, the
sqlpo development effort; however I hope I can offer some
contributions of value myself once I do. I do however want to share a
few thoughts:

1) My hat is off to the founders and active participants who are
moving this ball forward. It's great to see the interest and
enthusiasm, and I'm delighted to have the opportunity to get in fairly
close to the ground floor. I'm impressed with the quality of concern
and the gradual but continuous forward momentum the project seems to
retain. I appreciate the contributions that are being made.

2) Regarding some of the recent discussions of efficiency and
performance; these are clearly issues that matter – both in their own
right as well as in making sqlpo a viable contender among other
persistence options such as FMDB or even direct use of SQLite.
Several good suggestions have been made about opportunities for
improvement, and I suspect that over time we'll see and address many
more.

3) Regarding my own personal choice of which system to use – sqlpo has
my vote of confidence. The interface may not be the most efficient
available for all uses and users; and no single solution is a panacea
for best addressing everyone's needs. But the sqlpo approach is
exactly the kind of lite-weight, object-orient, implementation-hiding
interface I'm looking for and has impressed me as the best available
option of the many systems I've evaluated for my application needs.

We'll no doubt have a continuous stream of others who stop by to take
a gander and see if sqlpo meets their needs as well. Some will be
polite, others may engage in drive-by pot-shots. Most we'll never
hear from at all. It comes with the territory of an open discussion
group. Please accept my thanks for the good work to date, support for
ongoing documentation and enhancement, and encouragement for even
better things to come over time. I'm honored to be lurking here.

Thanks!
--Rophius

[Oliver Scheel]

> for best addressing everyone's needs.  But the sqlpo approach is
> exactly the kind of lite-weight, object-orient, implementation-hiding
> interface I'm looking for and has impressed me as the best available
> option of the many systems I've evaluated for my application needs.

Yes, that's it. I am new to obj-c and even with the lack of typical
documentation and tutorials, I was able to set up a working object
model within one day. Before I started to use sqlpo I already started
to write my own mini-ORM, but what a luck that I have googled
again ;-)

I have used other ORM solutions (EOF, SQLAlchemy, Hibernate, "EJB") in
other projects before and I must say that sqlpo is currently the best
solution for an ORM layer on the iPhone! I hope that it won't get
oversized, so please keep it simple stupid ;-)

Thanks to everyone!

Oliver