Would a Solstice/Database.pm replacement be enough?
There aren't currently any plans. We've been pretty focused on MySQL
- so even after replacing methods in Solstice::Database, the SQL that
lives in Solstice and the applications might rely on MySQL extensions
to SQL. Additionally, we try to create the app's database the first
time an app is run, and those database definitions are definitely
MySQL specific.
We have on occasion subclassed Sol::DB in applications to connect to
either other hosts, or other db engines, but that's always been
exclusive to an application. The Solstice data continued to live in
MySQL while the app did its own thing.
If we wanted to support multiple db engines long term, I think we'd
need to move wholesale over to something like DBIx::Class, and get out
of the database business.
-Patrick A Michaud
> --
> You received this message because you are subscribed to the Google Groups
> "solstice-discussion" group.
> To post to this group, send email to solstice-...@googlegroups.com.
> To unsubscribe from this group, send email to
> solstice-discus...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/solstice-discussion?hl=en.
>
>