Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
pike
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
pikelang
pike
Commits
a45c4af2
Commit
a45c4af2
authored
7 years ago
by
Stephen R. van den Berg
Browse files
Options
Downloads
Patches
Plain Diff
Spelling fixes.
parent
52355b8f
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
lib/modules/Sql.pmod/Sql.pike
+1
-1
1 addition, 1 deletion
lib/modules/Sql.pmod/Sql.pike
with
1 addition
and
1 deletion
lib/modules/Sql.pmod/Sql.pike
+
1
−
1
View file @
a45c4af2
...
...
@@ -29,7 +29,7 @@
//! works well. That means at least that SQL integer fields are
//! returned as pike integers, floats as floats, SQL NULL as
//! @[Val.null], and of course strings still as strings. The
//! representation of other SQL types depend on the capabilities of
//! representation of other SQL types depend
s
on the capabilities of
//! the server specific backends. It's also possible that floats in
//! some cases are represented in other ways if too much precision is
//! lost in the conversion to pike floats.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment