Drop 01-spelling-error-in-manpage.patch, applied upstream.
gregor herrmann
3 years ago
0 | Description: Correct spelling errors in manpages | |
1 | Author: Nick Morrott <knowledgejunkie@gmail.com> | |
2 | Bug: https://rt.cpan.org/Ticket/Display.html?id=116765 | |
3 | Last-Update: 2016-08-07 | |
4 | --- | |
5 | --- a/lib/DBIx/SearchBuilder.pm | |
6 | +++ b/lib/DBIx/SearchBuilder.pm | |
7 | @@ -812,7 +812,7 @@ | |
8 | ||
9 | Example: | |
10 | ||
11 | -Suppose you want to create Limit statments which would produce results | |
12 | +Suppose you want to create Limit statements which would produce results | |
13 | the same as the following SQL: | |
14 | ||
15 | SELECT * FROM Users WHERE EmailAddress OR Name OR RealName OR Email LIKE $query; | |
16 | --- a/lib/DBIx/SearchBuilder/Handle.pm | |
17 | +++ b/lib/DBIx/SearchBuilder/Handle.pm | |
18 | @@ -816,7 +816,7 @@ | |
19 | If there is no transaction in progress then method throw | |
20 | warning unless action is forced. | |
21 | ||
22 | -Method returns true on success or false if error occured. | |
23 | +Method returns true on success or false if error occurred. | |
24 | ||
25 | =cut | |
26 | ||
27 | --- a/lib/DBIx/SearchBuilder/Record.pm | |
28 | +++ b/lib/DBIx/SearchBuilder/Record.pm | |
29 | @@ -139,7 +139,7 @@ | |
30 | ||
31 | =back | |
32 | ||
33 | -And really, thats it. So lets have some sample code. | |
34 | +And really, that's it. So lets have some sample code. | |
35 | ||
36 | =head2 An Annotated Example | |
37 | ||
38 | @@ -199,7 +199,7 @@ | |
39 | ||
40 | Here we set our handle and table name, while its not obvious so far, we'll | |
41 | see later that $handle (line: 006) gets passed via ::Record::new when a | |
42 | -new instance is created. Thats actually an important concept, the DB handle | |
43 | +new instance is created. That's actually an important concept, the DB handle | |
44 | is not bound to a single object but rather, its shared across objects. | |
45 | ||
46 | 013: | |
47 | @@ -286,12 +286,12 @@ | |
48 | 015: print "Foo : ", $s->Foo(), "\n"; | |
49 | 016: print "Bar : ", $s->Bar(), "\n"; | |
50 | ||
51 | -Thats all you have to to get the data, now to change the data! | |
52 | +That's all you have to to get the data, now to change the data! | |
53 | ||
54 | 017: | |
55 | 018: $s->SetBar('NewBar'); | |
56 | ||
57 | -Pretty simple! Thats really all there is to it. Set<Field>($) returns | |
58 | +Pretty simple! That's really all there is to it. Set<Field>($) returns | |
59 | a boolean and a string describing the problem. Lets look at an example of | |
60 | what will happen if we try to set a 'Id' which we previously defined as | |
61 | read only. | |
62 | @@ -331,7 +331,7 @@ | |
63 | ||
64 | And its gone. | |
65 | ||
66 | -For simple use, thats more or less all there is to it. In the future, I hope to exapand | |
67 | +For simple use, that's more or less all there is to it. In the future, I hope to exapand | |
68 | this HowTo to discuss using container classes, overloading, and what | |
69 | ever else I think of. | |
70 | ||
71 | @@ -1024,7 +1024,7 @@ | |
72 | current column value as argument. It uses the array reference as | |
73 | the object constructor's arguments. | |
74 | Subclasses can override _Object to insert custom access control or | |
75 | -define default contructor arguments. | |
76 | +define default constructor arguments. | |
77 | ||
78 | Note that if you are using a C<Schema> with a C<REFERENCES> field, | |
79 | this is unnecessary: the method to access the column's value will | |
80 | --- a/lib/DBIx/SearchBuilder/SchemaGenerator.pm | |
81 | +++ b/lib/DBIx/SearchBuilder/SchemaGenerator.pm | |
82 | @@ -88,7 +88,7 @@ | |
83 | ||
84 | =for public_doc CreateTableSQLText | |
85 | ||
86 | -Returns a string containg a sequence of SQL statements to create tables for all of | |
87 | +Returns a string containing a sequence of SQL statements to create tables for all of | |
88 | the models added to the SchemaGenerator. | |
89 | ||
90 | =cut |