Astroturfing was CoreData - large data set
Astroturfing was CoreData - large data set
- Subject: Astroturfing was CoreData - large data set
- From: "Marcus S. Zarra" <email@hidden>
- Date: Sun, 4 Dec 2005 11:28:59 -0700
Ruslan,
Do us all a favor please and comment on the entire reply not cutting
it up to just the pieces you care about. The OP had a question about
Core Data. Not about databases in general but about his Core Data
application. The solution was simple and had absolutely nothing to
do with your product. Your product may well be the second coming but
it still had nothing to do with the question.
If I post a question on the forum about Cocoa Bindings I really do
not want to hear from a Python developer how if I used Python I would
not have that problem.
Your constant referrals to your product are a form of astroturfing
and it is extremely distasteful.
On Dec 4, 2005, at 11:07 AM, Ruslan Zasukhin wrote:
On 12/4/05 7:34 PM, "Marcus S. Zarra" <email@hidden> wrote:
Hi Marcus,
This most recent question is a perfect example. The issue was
that the coder
needed to separate out the images to avoid his load time problem.
Switching to any other database would not have resolved that problem
without that separation of the data.
Moment please. Wrong.
I believe that it is me first have give such advice to Simon Liu.
Right, Marcus?
In next letter I did explain TECHNICAL issues why this trick help with
SqlLite.
Also I point that with Valentina there is no need to do such hacking.
Valentina perfectly eat your BLOBs in the same table.
So Valentina do resolve that problem.
Also note, having image in separate Table bring you one more index
search.
Compare to ZERO time if you keep BLOB in the same table.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden