Love Fuel?
Donate
About
Forums
Discussions
Login
FuelPHP Forums
Ask your question about FuelPHP in the appropriate forum, or help others by answering their questions.
WanWizard
a.k.a. WanWizard
Discussions
4
Comments
8243
Activity
created_at/updated_at inconsistencies
Correction, that is not possible. A submodule is a reference to a specific commit, after installing them your modules are 'headless', they don't point to any branch. If yours point to a specific branch, you must have done a "git…
Comment by
WanWizard
December 2012
permalink
created_at/updated_at inconsistencies
Yes, that is possible. Did I already mention I hate submodules? ;-) Pushed a fix to 1.5/develop.
Comment by
WanWizard
December 2012
permalink
created_at/updated_at inconsistencies
According to the "oil console" output, you're already on 1.5-dev. I use it in production everywhere, it's the quickest way for me to find stability issues. Most people stay on 1.4, so issues with 1.5 will only be reported after …
Comment by
WanWizard
December 2012
permalink
created_at/updated_at inconsistencies
I've just generated some code using scaffolding (on 1.5/develop), and everything seems to be there: properties, observers, and columns in the migration. What commandline did you exactly use to generate the code? And with which version of Fuel?
Comment by
WanWizard
December 2012
permalink
Relation many to many filter WHERE IN
Examine what this query does: It joins 'frocks' with 'frocks_sizes', which as it's a one-to-many will cause the 'frocks' part to be repeated. Then you select '*', meaning all fields from both tables. The…
Comment by
WanWizard
December 2012
permalink
Group problem
It's just a number and a name. As in "you are member of Administrators". If you want it to behave like a level ( so member(50) returns true if you are administrator), you'll have to extend the Auth driver class that provides th…
Comment by
WanWizard
December 2012
permalink
Relation many to many filter WHERE IN
Then I'm lost to what you're trying to do. You specify "frocks.brand_id = 19" and "frocks_sizes.size_id = 7", which for me are selection criteria, that have nothing to do with the join. From what I understood, you wan…
Comment by
WanWizard
December 2012
permalink
Group problem
The group is not a 'level' value, it's a discrete group id. So 1 !== 100.
Comment by
WanWizard
December 2012
permalink
Relation many to many filter WHERE IN
Like so: http://www.snipr.it/~tp
Comment by
WanWizard
December 2012
permalink
DB problem
Yes, it does, but you're looking at the wrong thing. Database results are always returned as a result instance, which is a container object that contains the resultset. Only when you access the individual results the data is converted to the f…
Comment by
WanWizard
December 2012
permalink
Modules?
Looks ok too. No routes that could interfere? Or a file rigths issue? Other then that I can't think of an immediate reason why this would fail, config, folder structure and class look fine.
Comment by
WanWizard
December 2012
permalink
Relation many to many filter WHERE IN
I can image that throws a SQL error, that's complete rubbish. You're 'or_on" clauses are selection criteria, and should be WHERE clauses.
Comment by
WanWizard
December 2012
permalink
Modules?
Looks ok. You've got the modules path configured in your config.php?
Comment by
WanWizard
December 2012
permalink
Relation many to many filter WHERE IN
1.5/develop supports multiple ON's on a JOIN, that is not available in 1.4.
Comment by
WanWizard
December 2012
permalink
Sqlite support
Most of the DB util methods are quite MySQL centric at the moment. We're going to switch DB layer in an upcoming version of Fuel to solve that issue.
Comment by
WanWizard
December 2012
permalink
Demo-Module
I know that, but posting code somewhere isn't going to change that will it? You asked for examples of what Oil generates, and I pointed you to the docs that have all those examples, and asked you what you want that isn't in there...
Comment by
WanWizard
December 2012
permalink
Propel?
Ok. It should not be to difficult to integrate Propel, in a package, either using a bootstrap file or with a secondary autoloader. We're going to switch to Cabinet, a new DB layer that does fully support MSSQL, so our ORM will soon do too.
Comment by
WanWizard
December 2012
permalink
Suitable package for simple forum / comment threads?
I'm not aware of a forum implemented in FuelPHP.
Comment by
WanWizard
December 2012
permalink
Relation many to many filter WHERE IN
so the problem is in the second or_having. As I wrote, you have to be careful when you use HAVING instead of WHERE. WHERE is a result selection (so it runs while selecting data for the result), while HAVING is a result filter, which is applied afte…
Comment by
WanWizard
December 2012
permalink
Demo-Module
That is in the docs. If you look at http://docs.fuelphp.com/packages/oil/generate.html, you can see all possible generate options, with examples, and the generated code. What else do you need?
Comment by
WanWizard
December 2012
permalink
Demo-Module
Ah, ok. Oil doesn't generate modules, it can generate a basic skeleton of a controller or a model. If you want some examples, you could look at http://github.com/fuel/depot. The code isn't finished, but it will absolutely give you some …
Comment by
WanWizard
December 2012
permalink
Relation many to many filter WHERE IN
Query looks ok. What happens if you paste this into something like phpmyadmin or the commandline sql tool? p..s if you don't have a GROUP BY, I would use WHERE instead of HAVING...
Comment by
WanWizard
December 2012
permalink
Relation many to many filter WHERE IN
Enable the profiler or use echo DB::last_query(); to check what SQL is exactly generated.
Comment by
WanWizard
December 2012
permalink
Problem running a query using the db class
If you don't specify a type, the DB query class with try to autodetect it. that works for "SELECT", "INSERT" and "CREATE". This type is then used by the DB drivers query method to determine what the expected retur…
Comment by
WanWizard
December 2012
permalink
get_index($id) doesn't work in Controller_Rest
I find that dangerous, because that means you'll route all unknown method requests to 'index' too, as the router doesn't know what is and isn't a valid param. By having to define a route for it, you explicitly define that t…
Comment by
WanWizard
December 2012
permalink
More Comments
Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Sign In
Apply for Membership
About
Username
WanWizard
Joined
January 2011
Visits
2,395
Last Active
July 6
Roles
Administrator