jlrdw

Have you tried the get method for returning back to Ajax.

Just a quick thought on it have you checked your letter case Linux is case sensitive.

did you even bother to look at the link I gave. You get answers to your questions but you are always ignoring.

@TOWHID - Remember, clear cache after changes.

I think OP means what is currently stored in the DB. (I think)

See https://laracasts.com/discuss/channels/laravel/how-do-i-assign-the-existing-value-to-a-select

By retrieving what's stored just like inputs.

learning Laravel ways

No arguments here but very vague.

For simple relation ORM is fine, but for more complex I perfer this style:

$quy = Powner::query()->leftJoin('dc_pets', 'dc_powners.ownerid', '=', 'dc_pets.ownerid')
                ->select('dc_powners.ownerid', 'dc_powners.oname')
                ->selectRaw('count(dc_pets.petid) as countOfPets')
                ->groupby('dc_powners.ownerid')
                ->orderby('dc_powners.oname')
                ->get();

Results basically give:

ownerid, oname, countOfPets

Like:

5|Bob|3
4|Greg|9
2|Rob|1

After QB, Eloquent, (active record) it goes through the various methods which determine what type relation and exactly what query type is needed it's all done via normal PDO:

Quote:

    public function select($query, $bindings = [], $useReadPdo = true)
    {
        return $this->run($query, $bindings, function ($query, $bindings) use ($useReadPdo) {
            if ($this->pretending()) {
                return [];
            }
            // For select statements, we'll simply execute the query and return an array
            // of the database result set. Each element in the array will be a single
            // row from the database table, and will either be an array or objects.
            $statement = $this->prepared($this->getPdoForSelect($useReadPdo)
                              ->prepare($query));
            $this->bindValues($statement, $this->prepareBindings($bindings));
            $statement->execute();
            return $statement->fetchAll();
        });
    }

Unquote as example

Which is not the same but similar to a framework I contributed to:

    public function select($sql, $array = array(), $fetchMode = PDO::FETCH_OBJ, $class = '')
    {
        $stmt = $this->prepare($sql);
        foreach ($array as $key => $value) {
            if (is_int($value)) {
                $stmt->bindValue("$key", $value, PDO::PARAM_INT);
            } else {
                $stmt->bindValue("$key", $value);
            }
        }

        $stmt->execute();

        if ($fetchMode === PDO::FETCH_CLASS) {
            return $stmt->fetchAll($fetchMode, $class);
        } else {
            return $stmt->fetchAll($fetchMode);
        }
    }

Where $array is the bindings.

In fact Active record reduces down to this at runtime:

$sql = "SELECT dc_powners.ownerid, dc_powners.oname, ";
          $sql .= "COUNT(dc_pets.petid) AS CountOfpetid ";
          $sql .= "FROM dc_powners LEFT JOIN dc_pets ON ";
          $sql .= "dc_powners.ownerid = dc_pets.ownerid ";
          $sql .= "GROUP BY dc_powners.ownerid ";
          $sql .= "ORDER BY dc_powners.oname";

In other words regular sql

Many here write queries laravel agnostic, which is fine.

But I like queries that can easily be brought over to another framework is needed.

For example the above works here, yii2, or cakephp. All the major frameworks have the PDO instance.

And eloquent uses the exact same.

No arguments, but if you want active record fine, but don't judge one if they prefer normal queries if the query is a little more complex. I in fact prefer getPdo() for many things.

Taylor doesn't force any "way" of getting DB results.

But if using normal sql use proper bindings as needed.

Just query what you need and just display it, merging the collection combines them, that's expected Behavior.

Look at query scopes.

You saying you can't have a table with roles.

You determine if a role matches.

Did you even follow my suggestion above as multiple tables has also been covered.

If solved, are you going to mark it solved.

If you are logging in a user in a framework like laravel and you do not understand how a cookie works in conjunction with session you probably need to take some basic tutorials.

The authorization and Authentication with multiple tables versus one table has been covered in the Forum very well before.

Google:

Site:laracasts.com your search term

There is many prior coverage is on this.

Can't understand why you would need something like Jasper reports with just a little bit of join and group by you can very easily write your own

Just examples

Also I just gave a quick answer a while back to someone looking for join and group by together.

This is just an example:

$quy = Powner::query()->leftJoin('dc_pets', 'dc_powners.ownerid', '=', 'dc_pets.ownerid')
                ->select('dc_powners.ownerid', 'dc_powners.oname')
                ->selectRaw('count(dc_pets.petid) as countOfPets')
                ->groupby('dc_powners.ownerid')
                ->orderby('dc_powners.oname')
                ->get();

Results basically give:

ownerid, oname, countOfPets

Like:

5|Bob|3
4|Greg|9
2|Rob|1
// more

@ETERNALCHAOS520 - It would not hurt you to take some real basic HTML JavaScript and PHP tutorials.

Perhaps some basic CSS also.

I have not deeply searched this, but one class depends on another class it takes some jumping around in the API two piece everything together.

https://laravel.com/api/5.8/Illuminate/Auth/Passwords/TokenRepositoryInterface.html#method_create

Search the API. It has links to where the code is also.

did you clear your config.

Have you read about pagination in the documentation.

Highly suggest some basics first:

https://www.w3schools.com/

• html
• css
• basic javascript
• php

A join and a group by example is something like

This is just an example:

$quy = Powner::query()->leftJoin('dc_pets', 'dc_powners.ownerid', '=', 'dc_pets.ownerid')
                ->select('dc_powners.ownerid', 'dc_powners.oname')
                ->selectRaw('count(dc_pets.petid) as countOfPets')
                ->groupby('dc_powners.ownerid')
                ->orderby('dc_powners.oname')
                ->get();

Results basically give:

ownerid, oname, countOfPets

Like:

5|Bob|3
4|Greg|9
2|Rob|1
// more

Example uses count just change to Max or whatever aggregate you need.

See https://laracasts.com/discuss/channels/eloquent/why-doesnt-laravel-use-joins-when-pulling-belongsto-or-hasone

Different query types are used for different purposes usually a master detail it's more like an invoice is the master and the details on that invoice would be the children.

Joins and group by are usually more for monthly and quarterly reports things like that.

So the type of query depends on what data you are trying to get and why.

Why don't you take some quality time relax a little and take some of Jefferies free video training.

It might just help you quite a bit.

Do you need mobile app or just mobile-friendly. Which is usually handled using media queries. And of course images are optimized for the web.

@WILK_RANDALL - Sorry I missed the "not".

We are lucky if some read the laravel docs, haha.

@WILK_RANDALL - I'm sure you meant case in-sensitive.

Was hoping OP would actually consult the MySql manual.

I am just guessing you are using mysql. Have you studied he chapters in the docs on sql selects, etc.

https://dev.mysql.com/doc/refman/8.0/en/

Run the query in your mysql front. I use sqlyog, but whatever you use. Learn a little, experiment a little.

See here https://laracasts.com/discuss/channels/laravel/i-want-to-create-two-types-user-panel-for-two-types-user

But a user is a user, you don't need separate tables, that's where Authorization comes in.

Authentication just means a login is required.

Posting with ajax and jquery has been covered so many times on this forum probably hundreds. I've given numerous examples myself.

Google:

site:laracasts.com ajax post
or
site:laracasts.com jquery ajax post

Good one to know.

Confused as to question, why not just follow the PSR coding specs. Which is what laravel follows.

The one extra query to get parent (master) is no big deal even if millions of users.

A join has to transverse over two tables.

You might want to take a basic sql tutorial. Or study the various selects, joins, etc here.

https://dev.mysql.com/doc/refman/8.0/en/

Again it depends on what data you need and how needed.

If you go to

yourtsite.com/laravel

replace yoursite.com with actual name you should see:

See what happens if you rename the folder that's above public_html to laravelup

And changing the lines to

/*
|--------------------------------------------------------------------------
| Register The Auto Loader
|--------------------------------------------------------------------------
|
| Composer provides a convenient, automatically generated class loader for
| our application. We just need to utilize it! We'll simply require it
| into the script here so that we don't have to worry about manual
| loading any of our classes later on. It feels great to relax.
|
*/

require __DIR__.'/../../laravelup/vendor/autoload.php';

/*
|--------------------------------------------------------------------------
| Turn On The Lights
|--------------------------------------------------------------------------
|
| We need to illuminate PHP development, so let us turn on the lights.
| This bootstraps the framework and gets it ready for use, then it
| will load up this application so that we can run it and send
| the responses back to the browser and delight our users.
|
*/

$app = require_once __DIR__.'/../../laravelup/bootstrap/app.php';

And your index.php goes

|- public_html
    |- laravel
         |- index.php   // here
         |-  css
         |-  js

You do have a RewriteBase in your htaccess.

You did point to main laravel with

../../

You should not be able to see the folder structure.

Let's be realistic if that complex query is already working just use as is.

There are times to use the orm and times that it's not as good.

Direct relations is better suited for orm.

If storing to a folder above public_html you setup a symbolic link:

https://laravel.com/docs/5.8/filesystem

Or many times on shared hosting you can upload to a folder underneath public_html.

You're overthinking this there are two styles of doing this one is as you suggest the other is like a monthly report.

For example company A with their receivables Company B and their receivables Etc.

Join is used a lot with a group by for a different style of report.

The two query technique is more like an invoice with the order details. In other words a Master detail or parent-child relationship.

So it depends on what data you need and how you need it.

@IRANKHOSRAVI - Just one question: In another post you had trouble uploading an image. Not edit, but upload.

So, did you ever get that working?

Why not start here:

https://www.w3schools.com/php7/ Then take Jeffrey's free courses.

when i ssh any php artisan command from terminal on my mac, i'm getting this error...

So your host is fine the problem is on your Mac in your development version.

If you go to your site and put in

Yoursite.com/.env

Of course replacing Yoursite.com with your site's actual name.

What do you get.

I would suggest just taking it slow and easy and realize like anyting there's a learning curve involved.

And practice by doing a small crud application.

There's quite a bit to be learned just working the examples in the documentation also.

Main laravel goes above public_html see

https://laracasts.com/discuss/channels/laravel/next-issue-fonts-and-images-arent-visible

The guide in that link is from snapey, it works correctly.

Otherwise your site is insecure.

Scopes

@SNAPEY - If you mean allows code to be executed repeatedly, and matched with the OP, I am following your advice.

@AP3TWE - Well I don't do that, but post here, even if I can't help @snapey and @cronix And @bobbybouwmann and @others are very good with laravel.

Me I came from Java at first and I usually don't write everything like Taylor might. But I've been doing this sice ild dbase 3 in the late 1980's.

Example I use laravel authentication, but have custom helpers to work with that. But I know how to implement RBAC. Iwas even a contributor to another framework.

I do not suggest someone new to write custom helpers, services until they have quite a bit of experience.

Understand when I did java, servlets, jsp, and ejb, there wasn't "out of box stuff". Back then you even wrote your own paginator as example.

And I only did business programming, I did logistics programming at a trucking / loistics company.

I am very "old" school. But I do enjoy trying to help folks. I am semi retired now.

In controller do this:

public function index()
{
    $slideshows = Slideshow::latest()->get();
    $services = Service::latest()->get();
    echo '<pre>';
        print_r($services);
        echo '</pre>';
        exit();
    $faqs = Faq::latest()->get();
    return view('Home.index', compact('slideshows', 'services', 'faqs'));
}

I can view a print_r much better than a var_dump. You need to study the exact results you are getting.

In your LoginController add:

    public function username()
    {
        return 'hd_username';
    }

And I am not 100% sure on the, but if that don't work try

Not in the construct function .

And change the forms as well.

I like query scopes, to fine tune things right in the query:

    public function scopegetPets($query, $petsearch = '')
    {
        $petsearch = $petsearch . "%";
        $query->where('petname', 'like', $petsearch);
        if (ChkAuth::userRole('admin') === false) {  // custom RBAC
            $userid = Auth::user()->id;
            $query->where('ownerid', '=', $userid);
        }
        $results = $query->orderBy('petname', 'asc')->paginate(5);
        return $results;
    }

Not a spatie example but just example of, if user is an admin they can see all, otherwise

the query only allows a user to see their own data.

Many times roles and permissions are used in conjunction with the way the query s written.

The above I have a custom helper class that works with laravel authentication.

But example was to show how a scope is helpful.

Also to play it extra safe I usually run request through strip_tags.

Something like:

   public static function fixValue($rvalue)
    {
        $rvalue = empty($rvalue) && !is_numeric($rvalue) ? NULL : trim(strip_tags($rvalue));
        return $rvalue;
    }

Not saying to use a static helper like me, use a getter setter or whatever.

It removes those dangerous tags.

Thanks for the code share.