For more than one database it seems that you are able to do it http://docs.djangoproject.com/en/dev/topics/db/multi-db/. You could implement your device functions inside something like myproject.device.functions if your not working with alot of data. Or you can implement that in the database handler.
Regards, Devin M On Oct 15, 12:25 pm, Damir Dezeljin <[email protected]> wrote: > Thanks. > > I read the docs you pointed med to and now I have few more questions: > 1. Is it possible to use two or more different back-ends with a single > Django project? For me it seems not. > > 2. After rethinking my needs I realized I need simple functions as e.g. > FlushDevice(), GetServerUptime(), AssignUserToDevice(), etc. This doesn't > really seem to be a lot of data so I'm wondering what do you suggest on how > or where to implement the required interfaces? > > Sincerely, > Damir > > On Fri, Oct 15, 2010 at 15:35, Devin M <[email protected]> wrote: > > Hello, > > It looks like you want a custom database backend. On > >http://docs.djangoproject.com/en/dev/ref/settings/?from=olddocs#engine > > they say > > "You can use a database backend that doesn't ship with Django by > > setting ENGINE to a fully-qualified path (i.e. > > mypackage.backends.whatever). Writing a whole new database backend > > from scratch is left as an exercise to the reader; see the other > > backends for examples." > > So i suppose you can look to the other backends for examples. > > > Regards, > > Devin Morin > > > On Oct 15, 6:21 am, Damir Dezeljin <[email protected]> wrote: > > > Hi. > > > > I'm working on an application tat communicates with embedded devices > > > connected to the LAN. The devices are controlled by a central server > > written > > > in C++. Django is used for the front-end or better to say the GUI for the > > > server. > > > > Part of the data the user needs access too are stored in the database, > > hence > > > the Django DB API to access this data; however, there are certain data > > and > > > actions that requires direct communication with the C++ server. The > > > communication is implemented using CORBA (OmniORBpy). E.g. of a situation > > > where the CORBA interface between the GUI and the server is needed is the > > > flush of devices configuration or update of the following and this should > > be > > > real time and not implemented polling the DB. > > > > Currenly I'm instantiating the CORBA interface to my server in the > > views.py. > > > I'm wondering if there is a better way to do it as I just don't see how > > > could I put the CORBA interface in the Model part of the GUI? << I'm > > still > > > confused by MVC approaches certain frameworks like CakePHP use. I think > > > Django is not such a framework; however, I still think I should somehow > > > separate the data layer from the business logic (bottomline: Django is > > still > > > kind of a MVC framework). How can I do this? > > > > Of course I would also like to solve the problem I'm currently facing: > > > Let's suppose both the C++ server and Django web site are up and running. > > If > > > the C++ server is restarted the web page doesn't work any more until when > > I > > > restart the web server too. I instantiate the CORBA object in a global > > > scope; however, I thought there is no persistence for the Django code > > > between the web browser calls. Am I right? Why the connection to CORBA > > > ceases working in such a case? << with e.g. C++ or Python stand-alone > > > clients the connection is reestablished each time the script / program / > > ... > > > is executed. > > > > Thanks for any hint you may have, > > > Damir > > > -- > > You received this message because you are subscribed to the Google Groups > > "Django users" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<django-users%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/django-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
