On Fri, Jul 8, 2011 at 4:01 PM, Hummingbird <vineet.deod...@gmail.com> wrote:
> @Cal,
> My apologies if my post has hurted you.
> I didn't mean that.
> I understand that all these open source projects are run by people who
> don't get paid for it.
>
> My point was quite different. It was about knowledge sharing.
> We can re-phrase the question if nobody understands what we mean to
> ask.
> Actually, we are not asking for any exact code or any spoon-feeding.
> We are asking whether anybody has developed a solution similar to
> CursorAdaptor in VFP
> Ed Leafe & Paul McNett have done marvelous work in this area (DABO
> desktop framework).
>
> Instead of making this post very long by giving details of what is a
> CursorAdaptor, pl. refer to --
> http://msdn.microsoft.com/en-us/library/d993hde7(v=vs.80).aspx
>
> Regarding your remark of "Don't expect an instant answer"--
> -- OP was dated 30th June.
> Today is 8th July (an instant???)
>
> Again, pl. excuse me if I have said anything wrong.
> @qMax:  Have you got any way around your question?
>
> ---Vineet
>

Hi Vineet

The problem both you and the OP have is that you asked extremely vague
questions. I've re-read the OPs post a number of times, and all I can
see is some extremely vague discussion on how the ORM represents
tables as model instances. I still don't see a question there, or at
least one I can answer.

Your question is only vaguely related to the OPs (in that it deals
with the ORM). On mailing lists, some people find replying to another
thread with a different question of your own almost as rude as TYPING
IN ALL CAPS. It is best to start a new thread rather than hijacking
someone elses. Secondly, continually bumping a thread each day is also
very annoying. Both of these things will dissuade people from replying
to you, so bear that in mind.

Netiquette apart, your question is vague. You describe a system where
by you can update various tables, updating the ones you want. This is
a basic feature of ORMs - have you read the tutorial or any of the
documentation on django's ORM?

I think the basic point is that you are far too vague about what you
want. You can't just point at us at some MS relational layer
documentation from 2005 and expect us to wade through it, work out
what you are currently doing, work out if that is applicable to
Django's ORM and formulate a plan for you. You are going to need to do
some of the work yourself.

There are more ORMs out there than you can imagine. You need to work
out what you want from a framework, and evaluate the frameworks out
there to find the suitable one for your project. We can help by
telling you about the Django one, but you need to help by telling us
what you want to do with it (consider creating, reading, updating and
deleting items as something that all the frameworks will do).

I think you will find people here will be willing and responsive to
help you, once you figure out what it is that you want from Django,
and start asking precise questions about what Django can support.

Cheers

Tom

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Reply via email to