underdarknl / uweb3 Goto Github PK

Currently the self.post will be set to the JSON result of a request when data is present, and if empty to an IndexedFieldStorage.

When the first class uses an SQLITE connector and the second class has no specification there will be a cross database fetch and join.
Class one will fetch from SQLITE, class two will fetch from MYSQL by default, resulting in a record that is combined with data from two different databases

This issue is present in the uweb3warehouse when the first request to the server is an API request.
In this case the decorator attempts to see if the user is registered in the database, however since the connection object has no connection present yet it will instead crash.

This might have something to do with the stackwalking that is done to find the correct connection object.
Still have to do some investigation to the exact cause.

When using the new implementation of routing routes are no longer being validated on presence.

This allows uweb3 to launch while a PageMaker does not have according route.

Currently all PageMakers are loaded into a 'super' PageMaker class that is passed to the uweb3 class when setting up the server.
This causes all PageMakers to be loaded on every request, even if the request is not meant for that PageMaker, thus losing the ability to write custom behaviour for a specific PageMaker.

Because of this it is not possible to use a PageMaker class to its full potential, we are missing out on functionality that was present in uweb2 such as _PostInit, _PostRequest, custom template dirs for specific PageMakers, and more.

A possible solution for this is the new routing proposed in #22 however this does not solve the issue for the current routing.

For example:

model.User.List(self.connection, order=("LOWER(username)",))

Will generate the following SQL:

ORDER BY `lower(username)`;

Thus generating an error because `lower(..)` is not a valid column.