Skip to content

Commit 22efc2c

Browse files
qoboodsvoj
authored andcommitted
Fix typos in C comments inside storage/
1 parent 3b3c512 commit 22efc2c

File tree

170 files changed

+315
-315
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

170 files changed

+315
-315
lines changed

storage/archive/azio.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -215,7 +215,7 @@ int write_header(azio_stream *s)
215215
int8store(ptr + AZ_CHECK_POS, (unsigned long long)s->check_point); /* Start of Data Block Index Block */
216216
int8store(ptr + AZ_AUTOINCREMENT_POS, (unsigned long long)s->auto_increment); /* Start of Data Block Index Block */
217217
int4store(ptr+ AZ_LONGEST_POS , s->longest_row); /* Longest row */
218-
int4store(ptr+ AZ_SHORTEST_POS, s->shortest_row); /* Shorest row */
218+
int4store(ptr+ AZ_SHORTEST_POS, s->shortest_row); /* Shortest row */
219219
int4store(ptr+ AZ_FRM_POS,
220220
AZHEADER_SIZE + AZMETA_BUFFER_SIZE); /* FRM position */
221221
*(ptr + AZ_DIRTY_POS)= (unsigned char)s->dirty; /* Start of Data Block Index Block */

storage/archive/ha_archive.cc

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -41,8 +41,8 @@
4141
4242
We keep a file pointer open for each instance of ha_archive for each read
4343
but for writes we keep one open file handle just for that. We flush it
44-
only if we have a read occur. azip handles compressing lots of records
45-
at once much better then doing lots of little records between writes.
44+
only if we have a read occur. azio handles compressing lots of records
45+
at once much better than doing lots of little records between writes.
4646
It is possible to not lock on writes but this would then mean we couldn't
4747
handle bulk inserts as well (that is if someone was trying to read at
4848
the same time since we would want to flush).
@@ -60,7 +60,7 @@
6060
6161
At some point a recovery method for such a drastic case needs to be divised.
6262
63-
Locks are row level, and you will get a consistant read.
63+
Locks are row level, and you will get a consistent read.
6464
6565
For performance as far as table scans go it is quite fast. I don't have
6666
good numbers but locally it has out performed both Innodb and MyISAM. For
@@ -1010,7 +1010,7 @@ int ha_archive::write_row(const uchar *buf)
10101010
temp_auto= table->next_number_field->val_int();
10111011

10121012
/*
1013-
We don't support decremening auto_increment. They make the performance
1013+
We don't support decrementing auto_increment. They make the performance
10141014
just cry.
10151015
*/
10161016
if (temp_auto <= share->archive_write.auto_increment &&

storage/archive/ha_archive.h

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ class Archive_share : public Handler_share
5252
/*
5353
Version for file format.
5454
1 - Initial Version (Never Released)
55-
2 - Stream Compression, seperate blobs, no packing
55+
2 - Stream Compression, separate blobs, no packing
5656
3 - One stream (row and blobs), with packing
5757
*/
5858
#define ARCHIVE_VERSION 3

storage/connect/array.h

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -107,7 +107,7 @@ class DllExport ARRAY : public XOBJECT, public CSORT { // Array descblock
107107
/* This class is used when constructing the arrays of constants used */
108108
/* for indexing. Its only purpose is to provide a way to sort, reduce */
109109
/* and reorder the arrays of multicolumn indexes as one block. Indeed */
110-
/* sorting the arrays independantly would break the correspondance of */
110+
/* sorting the arrays independently would break the correspondence of */
111111
/* column values. */
112112
/***********************************************************************/
113113
class MULAR : public CSORT, public BLOCK { // No need to be an XOBJECT

storage/connect/csort.cpp

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ CSORT::CSORT(bool cns, int th, int mth)
9595
} // end of CSORT constructor
9696

9797
/***********************************************************************/
98-
/* CSORT intialization. */
98+
/* CSORT initialization. */
9999
/***********************************************************************/
100100
int CSORT::Qsort(PGLOBAL g, int nb)
101101
{

storage/connect/filamgz.cpp

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -339,7 +339,7 @@ int GZFAM::ReadBuffer(PGLOBAL g)
339339
*p = '\0'; // Eliminate ending new-line character
340340

341341
if (*(--p) == '\r')
342-
*p = '\0'; // Eliminate eventuel carriage return
342+
*p = '\0'; // Eliminate eventual carriage return
343343

344344
strcpy(Tdbp->GetLine(), To_Buf);
345345
IsRead = true;

storage/connect/filamtxt.cpp

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -352,7 +352,7 @@ int TXTFAM::StoreValues(PGLOBAL g, bool upd)
352352
/* record are not necessarily updated in sequential order. */
353353
/* Moving intermediate lines cannot be done while making them because */
354354
/* this can cause extra wrong records to be included in the new file. */
355-
/* What we do here is to reorder the updated records and do all the */
355+
/* What we do here is reorder the updated records and do all the */
356356
/* updates ordered by record position. */
357357
/***********************************************************************/
358358
int TXTFAM::UpdateSortedRows(PGLOBAL g)
@@ -402,7 +402,7 @@ int TXTFAM::UpdateSortedRows(PGLOBAL g)
402402
/***********************************************************************/
403403
/* DeleteSortedRows. When deleting using indexing, the issue is that */
404404
/* record are not necessarily deleted in sequential order. Moving */
405-
/* intermediate lines cannot be done while deleing them because */
405+
/* intermediate lines cannot be done while deleting them because */
406406
/* this can cause extra wrong records to be included in the new file. */
407407
/* What we do here is to reorder the deleted record and delete from */
408408
/* the file from the ordered deleted records. */

storage/connect/filter.cpp

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -547,7 +547,7 @@ bool FILTER::FindJoinFilter(POPJOIN opj, PFIL fprec, bool teq, bool tek,
547547
return (Opc < 0);
548548

549549
// Keep only equi-joins and specific joins (Outer and Distinct)
550-
// Normally specific join operators comme first because they have
550+
// Normally specific join operators come first because they have
551551
// been placed first by SortJoin.
552552
if (teq && Opc > OP_EQ)
553553
return FALSE;
@@ -747,7 +747,7 @@ bool FILTER::CheckHaving(PGLOBAL g, PSQL sqlp)
747747
return FALSE;
748748
default:
749749
if (CheckColumn(g, sqlp, xp, agg) < -1)
750-
return TRUE; // Unrecovable error
750+
return TRUE; // Unrecoverable error
751751

752752
break;
753753
} // endswitch Opc

storage/connect/fmdlex.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -845,7 +845,7 @@ static int yy_get_next_buffer()
845845
{ /* Don't try to fill the buffer, so this is an EOF. */
846846
if ( yy_c_buf_p - yytext_ptr - YY_MORE_ADJ == 1 )
847847
{
848-
/* We matched a singled characater, the EOB, so
848+
/* We matched a singled character, the EOB, so
849849
* treat this as a final EOF.
850850
*/
851851
return EOB_ACT_END_OF_FILE;

storage/connect/ha_connect.cc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4990,7 +4990,7 @@ int ha_connect::external_lock(THD *thd, int lock_type)
49904990
} // endelse Xchk
49914991

49924992
if (CloseTable(g)) {
4993-
// This is an error while builing index
4993+
// This is an error while building index
49944994
// Make it a warning to avoid crash
49954995
push_warning(thd, Sql_condition::WARN_LEVEL_WARN, ER_UNKNOWN_ERROR, g->Message);
49964996
rc= 0;

0 commit comments

Comments
 (0)