<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Variable Scope on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</title>
    <link>https://ronaldbradford.com/tags/variable-scope/</link>
    <description>Recent content in Variable Scope on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 03 Jun 2010 18:43:24 +0000</lastBuildDate>
    <atom:link href="https://ronaldbradford.com/tags/variable-scope/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>When SET GLOBAL affects SESSION scope</title>
      <link>https://ronaldbradford.com/blog/when-set-global-affects-session-scope-2010-06-03/</link>
      <pubDate>Thu, 03 Jun 2010 18:43:24 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/when-set-global-affects-session-scope-2010-06-03/</guid>
      <description>We have all been caught out with using SET and not realizing that the default GLOBAL Scope (since 5.0.2) does not change the current SESSION scope.&#xA;I was not aware until today that changing GLOBAL scope has some exceptions that also automatically affect SESSION scope.</description>
    </item>
  </channel>
</rss>
