Hi, over at Stack Overflow a user has a strange table size reported
(2.1,000,000,000,000,000,888 KiB; after running REPAIR one other table's
similar problem was fixed). This seems odd, our rounding of this number
should not produce such a strange number. Has anyone seen anything
similar to this? One table affected for one user doesn't make a very
good bug report, but if there's a shortcoming we of course want to try
to fix it. Any thoughts?
Hi, a user on Stackoverflow is reporting that their Import and Export
links don't show the main page; he/she sees the navigation pane, menu
bar, and console but no content in the main pane. Any thoughts about
what could cause that behavior? Report and screenshot at
You may have already noticed, but a few weeks ago Github rolled out a
new feature where you can select what type of merge to perform when
merging a pull request. It appears you can now squash and rebase commits
by clicking the confirmation dropdown, rather than performing an actual
merge commit. This seems like a helpful feature.
Currently, the release instructions prompt me to create a MAINT branch
for each release. That way, if we have a security fix for 4.6.2 we can
go to MAINT_4_6_2 and perform the work there. I think this is overkill
-- for instance, we haven't done a patch-level security release on 4.6.0
If we need to do a security release, we can create the MAINT branch later:
git checkout RELEASE_4_6_2
git checkout -b MAINT_4_6_2
I'm proposing that we stop creating MAINT branches for each release.
This isn't something I feel particularly strongly about, so I could be
convinced to withdraw my proposal, but I don't see much value in
maintaining MAINT branches we aren't using.
A side-effect of this is that currently, the demo server has STABLE,
QA_4_6, and MAINT_4_6_2 ; QA_4_6 will change until our next release
and STABLE and MAINT_4_6_2 will remain the same unless we need to
release a 184.108.40.206, in which case both would be updated. For the demo
server, I may be missing a scenario but don't see how the current MAINT
and STABLE would differ, meaning we can remove MAINT from there as well.
1 - technically, the demo server currently has MAINT_4_6_1, but based on
response to this thread I'll update it soon.
I constructed a minimum example:
Create a table (I called mine "Stuff") - first column, integer,
unsigned, primary key.
Second column, integer, unsigned, unique index.
The icon shown is a slightly less saturated primary index icon, NOT the
unique one (which has a red U)