On Tue, Apr 16, 2019 at 12:50:27PM +0200, Markus Elfring
<markus.elfr...@web.de> wrote:
> > No, I don't see a reason for a new class. New class could override
> > existing methods but we're talking about new method(s) so
> > why not add them just to SQLObject's main class?
>
> A command like ???CREATE TABLE??? belongs to the category ???data definition
> language???
> within SQL.
> I would prefer then that corresponding classes will be loaded (or imported)
> only if the code for such functionality will be used at all finally.
That's not how SQLObject is structured and intended to be used. In
SQLObject one has classes that correspond to tables:
class MyTable(SQLObject):
name = StringCol()
and the classes and their instances are used to query database. One can
create the table with ``MyTable.createTable()`` and query it with
``MyTable.select()``. You cannot split ``SQLObject`` class into plugins
that could be loaded only when needed.
> >>> SQLObject does some limited introspection.
> >>
> >> Would you like to improve the software situation in this area?
>
> Will the software documentation be extended also?
It'd be best if a pull request or a patch will be accompanied with
tests and docs.
> Regards,
> Markus
Oleg.
--
Oleg Broytman https://phdru.name/ p...@phdru.name
Programmers don't die, they just GOSUB without RETURN.
_______________________________________________
sqlobject-discuss mailing list
sqlobject-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
