Re: [Tutor] Multiple DBs per application?
On 14/05/12 20:33, leam hall wrote: Just a general question. If you have an application with different data types where it might be better to use one database over another, are there issues with having multiple databases used by the application? No, you can usuially have multiple databases open at once. You can have multiple instances of the same database or different database types. However the data types are rarely ta reason to use different databases. More typically would be different performance requirements or security issues. For example it's common to hold some data in an LDAP structure for speed of access (at the expense of flexibility) and the rest of the data in an RDBMS such as MySql. But using say MySQL and Oracle together would normally only be done because they were pre-existing datastores from another project. -- Alan G Author of the Learn to Program web site http://www.alan-g.me.uk/ ___ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: http://mail.python.org/mailman/listinfo/tutor
Re: [Tutor] Multiple DBs per application?
On 05/14/2012 06:44 PM, Alan Gauld wrote: On 14/05/12 20:33, leam hall wrote: Just a general question. If you have an application with different data types where it might be better to use one database over another, are there issues with having multiple databases used by the application? No, you can usuially have multiple databases open at once. You can have multiple instances of the same database or different database types. However the data types are rarely ta reason to use different databases. More typically would be different performance requirements or security issues. For example it's common to hold some data in an LDAP structure for speed of access (at the expense of flexibility) and the rest of the data in an RDBMS such as MySql. But using say MySQL and Oracle together would normally only be done because they were pre-existing datastores from another project. Thanks! I was more thinking of something like a CMS where user login information and admin functions might be in a SQLite database and then some larger backend big data stuff in MongoDB or similar. Just wasn't sure if there was a basic flaw to the idea that I wasn't aware of. Leam ___ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: http://mail.python.org/mailman/listinfo/tutor
Re: [Tutor] Multiple DBs per application?
On 5/14/2012 3:33 PM, leam hall wrote: All, Just a general question. If you have an application with different data types where it might be better to use one database over another, are there issues with having multiple databases used by the application? BY database do you mean a table (as in dBase) a collection of tables (as an Access file) a database management system (MySQL)? -- Bob Gailer 919-636-4239 Chapel Hill NC ___ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: http://mail.python.org/mailman/listinfo/tutor
Re: [Tutor] Multiple DBs per application?
On 5/14/2012 7:55 PM, Leam Hall wrote: On 05/14/2012 06:44 PM, Alan Gauld wrote: On 14/05/12 20:33, leam hall wrote: Just a general question. If you have an application with different data types where it might be better to use one database over another, are there issues with having multiple databases used by the application? No, you can usuially have multiple databases open at once. You can have multiple instances of the same database or different database types. However the data types are rarely ta reason to use different databases. More typically would be different performance requirements or security issues. For example it's common to hold some data in an LDAP structure for speed of access (at the expense of flexibility) and the rest of the data in an RDBMS such as MySql. But using say MySQL and Oracle together would normally only be done because they were pre-existing datastores from another project. Thanks! I was more thinking of something like a CMS where user login information and admin functions might be in a SQLite database and then some larger backend big data stuff in MongoDB or similar. Just wasn't sure if there was a basic flaw to the idea that I wasn't aware of. Seems like a good idea. Right tool for right purpose. -- Bob Gailer 919-636-4239 Chapel Hill NC ___ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: http://mail.python.org/mailman/listinfo/tutor