While there continue to be some issues with Selenium tests (failures when there shouldn’t be), PBooks 0.08 is almost ready for release.
Installation has been a significant hurdle for many people so in ticket 138 I have specified the need to test out a complete install prior to release. An installation into a webserver docroot will be tested, as even though it is not recommended, many users on shared hosts find it easier to do so.
I’m very pleased to report that there has been some seriously major progress towards running PBooks with SQlite. The major hurdle was the way that I had structured SQL statements with “LEFT JOIN”. Once I found a better way to draft them, specifically using “INNER JOIN”, the incompatibility went away.
Besides the JOIN issue, I also had to remove the use of SUBSTRING and DATE MySQL functions. Unfortunately those are not the same in SQlite. Instead I’ll write an action to use PHP’s substring, as I’m sure that will still be faster than XSL’s substring capabilities.
Also note that there are two new SQL files - one for the structure and one for some sample data. Using SQLite with PBooks is still very far from being complete, but its a lot closer than it was a few hours ago!
For more information, see PBooks and SQLite
I’m working more on invoices and deposits, focusing on the ability to connect the two. When making a deposit, it would be very useful to attribute a payment to an invoice. Similarly, since business processes are fairly unique to each business and business type, I’ve been working on account transfers, and the creation of a check object if the transfer method is a check, as opposed to an electronic transfer.
I’m quite pleased with how the business processes / objects are coming along - they need a lot more refinement, but I’m comfortable enough with the progress made so far that I’m willing to do the refinement. (See ticket #124 for more information. )
An obvious refinement will be the offloading of complex Xpath queries to SQL JOINs. This will improve the application performance, but will also make the SQL less flexible. As I said, now that I’m comforable with the business objects, that shouldn’t be problem.
Latest Comments
RSS