Don't Create New Objects Each Time Open Shared Page

[Schwad]

  def shared
    @query = Query.create(
        :content => params[:format]
        )
    creates_checks(@query)
    creates_credit_cards(@query)
    @query.save

  end

Currently a new object is built from params each time a special shared page is viewed. The concept was to find a way to share a query page without opening up access to the User's private account page. Perhaps we can manually pull in a .where match with the params and showcase the data that way. (As we DO know if a query is shared it will most likely currently exist in our system. That our build two objects on each query, one to be accessed by public facing and one to be accessed private facing. Perhaps too dangerous)

[Schwad]

Well well well, looks like I found the annoying pest. A legacy era MVP codebase had new batches of queries, checks and credit cards made every time someone visited the "shared" page. Annoying! Also added about 4 million unnecessary objects in our database and broke postgres. all fixed!

Now it just grabs the params and points it to the current query/check in house, much quicker and cleaner.

AND if someone tries to reverse engineer our params it catches that and redirects now to the alternate view seen below.