kohana-3

问题 I need to know how to apply the "matches" validation rule in Kohana 3.1. I've tried the following rule in my model with no success: 'password_confirm' => array( array('matches', array(':validation', ':field', 'password')), ) But it always fails. I put a var_dump($array) in the first line of the Valid::matches() method. I paste it below: /** * Checks if a field matches the value of another field. * * @param array array of values * @param string field name * @param string field name to match *

问题 I noticed that Kohana 3 ORM runs a "SHOW FULL COLUMNS" for each of my models when I start using them: SHOW FULL COLUMNS FROM `mytable` This query might take a few clock cycles to execute (in the Kohana profiler it's actually the slowest of all queries ran in my current app). Is there a way to help Kohana 3 ORM to speed up by disabling this behaviour and explicitly define the columns in my models instead? 回答1: biakaveron answered my question with a comment so I can't except the correct answer.

问题 It seems that in v3.1.0 of Kohana's ORM that the _ignored_columns property has been removed. What the is the recommended technique to dealing with fields that aren't in the databases? The case I have right now is password_confirm where password is a field, but we require the user to enter their password twice. 回答1: You can pass an extra validation object to save, create and update. So your example would look like: /** * Password validation for plain passwords. * * @param array $values *

问题 I'm learning the framework, and now building an application using it. I need to get all users that have 'user' or 'staff' role, but I couldn't find about it on the documentation. Help anyone? (I think it's more an ORM problem the the auth module) 回答1: I didn't find an easy way to do this using the ORM, but I have a workaround. This is my code for anyone who might encounter the same problem with me. // One for each role $staffs = ORM::factory('role', array('name' => 'staff'))->users->find_all(

问题 I have a requirement to create custom exception for the exceptions generated by my app/module. I want to consolidate all the exception classes in one place and handle the exceptions in one place. I might have generic exceptions, like mentioned below, which I would like in one common place input invalid internal error (database errors, smtp errors, other failures) permission denied session error I might have specific exceptions, like mentioned below email not valid, etc. Specific exceptions

问题 In Kohana 2 you could easily get that information like this: echo router::$controller; echo router::$method; echo router::$arguments[0-x]; Any idea how that works in Kohana 3? Thanks in advance! 回答1: From inside a controller: $this->request->controller $this->request->action $this->request->param('paramname') Unlike K2 arguments in K3 are accessed via kays which you define in your routes. Take for example this url: Route::set('default', '(<controller>(/<action>(/<id>)))') ->defaults(array(

问题 I am trying to set up a product object in Kohana 3.3 using the built in ORM. I want it so that when I call: $p1 = ORM::factory('product') ->where('product_type', '=', '1') ->find_all(); it will create an object of this structure: Model_Product Object ( [_long_list_of_kohana_properties] => Array () [_object:protected] => Array ( [id] => 2 [product_type] => 1 ... [product_attributes] => Array (List of attributes) ) ) Currently, it produces this: Model_Product Object ( [_long_list_of_kohana

问题 I've just came across this on GitHub. ($config === NULL) and $config = Kohana::config('email'); Is that the equivalent of if ($config === NULL) { $config = Kohana::config('email'); } Is this commonplace? Would I expect other developers looking at my code if I used that first way to instantly know what it was doing? 回答1: Took me a second to get it, but that should actually work in just about every programming language. Because the "and" or "or" operators are lazily evaluated, if the statement

问题 How can this be done? I'm trying to do this for about half an hour and it's getting pretty annoying. You would this this should be an basic and easy thing to setup for a framework like this. I hope maybe there's an easy way i missed, because i'm starting to thing i should not chose this framework at all if such basic tings are so hard to setup. This is in my bootstrap.php file that should do the trick. if ( ! defined('SUPPRESS_REQUEST')) { /** * Execute the main request. A source of the URI

问题 I have a problem using Kohana 3.1. I add the old banks kohana-email module but the result is a error like this: ErrorException [ Fatal Error ]: Class 'Email' not found My application bootstrap.php file is like this: Kohana::modules(array( 'user' => MODPATH.'user', // Useradmin module 'auth' => MODPATH.'auth', // Basic authentication // 'cache' => MODPATH.'cache', // Caching with multiple backends // 'codebench' => MODPATH.'codebench', // Benchmarking tool 'database' => MODPATH.'database', //