• Facebook Page: 313037412072272
  • Linked In: in/billbernhardt
  • Twitter: #!/Harper_Creek
Home Custom Fly Rods Why a Custom Fly Rod is Better

Why a custom rod is better than a factory rod

Why is custom rod a better than a factory rod?


     A custom rod is better because each rod is built with a particular customer in mind instead of with the intention of appealing to a large mass of people.  Also, a custom rod is designed to each customer’s individual specifications with considerable thought given to the type of fishing each customer pursues in conjunction with their individual style of fly fishing. In addition, each custom rod is individually and meticulously hand-crafted to exacting standards with extreme attention paid to detail that is simply not possible with a mass-produced factory rod. Last, by purchasing a custom rod, each customer is able to choose from a large selection of rod blanks and components as well as the color and detail of the guide wraps to create a rod that is uniquely theirs and is perfectly suited to their individual needs and tastes.

 

•Profile Information•

Application afterLoad: 0.000 seconds, 0.70 MB
Application afterInitialise: 0.016 seconds, 1.45 MB
Application afterRoute: 0.023 seconds, 2.30 MB
Application afterDispatch: 0.039 seconds, 2.91 MB
Application afterRender: 0.156 seconds, 4.00 MB

•Memory Usage•

4258120

•11 queries logged•

  1. SELECT *
      FROM jos_session
      WHERE session_id = 'fi6tbodtvsjokao79lg4bfm1t3'
  2. DELETE
      FROM jos_session
      WHERE ( time < '1558856934' )
  3. SELECT *
      FROM jos_session
      WHERE session_id = 'fi6tbodtvsjokao79lg4bfm1t3'
  4. INSERT INTO `jos_session` ( `session_id`,`time`,`username`,`gid`,`guest`,`client_id` )
      VALUES ( 'fi6tbodtvsjokao79lg4bfm1t3','1558857834','','0','1','0' )
  5. SELECT *
      FROM jos_components
      WHERE parent = 0
  6. SELECT folder AS type, element AS name, params
      FROM jos_plugins
      WHERE published >= 1
      AND access <= 0
      ORDER BY ordering
  7. SELECT m.*, c.`option` AS component
      FROM jos_menu AS m
      LEFT JOIN jos_components AS c
      ON m.componentid = c.id
      WHERE m.published = 1
      ORDER BY m.sublevel, m.parent, m.ordering
  8. SELECT template
      FROM jos_templates_menu
      WHERE client_id = 0
      AND (menuid = 0 OR menuid = 201)
      ORDER BY menuid DESC
      LIMIT 0, 1
  9. SELECT a.*, u.name AS author, u.usertype, cc.title AS category, s.title AS section, CASE WHEN CHAR_LENGTH(a.alias) THEN CONCAT_WS(":", a.id, a.alias) ELSE a.id END AS slug, CASE WHEN CHAR_LENGTH(cc.alias) THEN CONCAT_WS(":", cc.id, cc.alias) ELSE cc.id END AS catslug, g.name AS groups, s.published AS sec_pub, cc.published AS cat_pub, s.access AS sec_access, cc.access AS cat_access 
      FROM jos_content AS a
      LEFT JOIN jos_categories AS cc
      ON cc.id = a.catid
      LEFT JOIN jos_sections AS s
      ON s.id = cc.section
      AND s.scope = "content"
      LEFT JOIN jos_users AS u
      ON u.id = a.created_by
      LEFT JOIN jos_groups AS g
      ON a.access = g.id
      WHERE a.id = 190
      AND (  ( a.created_by = 0 )    OR  ( a.state = 1
      AND ( a.publish_up = '0000-00-00 00:00:00' OR a.publish_up <= '2019-05-26 08:03:54' )
      AND ( a.publish_down = '0000-00-00 00:00:00' OR a.publish_down >= '2019-05-26 08:03:54' )   )    OR  ( a.state = -1 )  )
  10. UPDATE jos_content
      SET hits = ( hits + 1 )
      WHERE id='190'
  11. SELECT id, title, module, position, content, showtitle, control, params
      FROM jos_modules AS m
      LEFT JOIN jos_modules_menu AS mm
      ON mm.moduleid = m.id
      WHERE m.published = 1
      AND m.access <= 0
      AND m.client_id = 0
      AND ( mm.menuid = 201 OR mm.menuid = 0 )
      ORDER BY position, ordering

•Language Files Loaded•

•Untranslated Strings Diagnostic•

•None•

•Untranslated Strings Designer•

•None•