Npgsql Api Docs |

# NpgsqlTypes Namespace

Namespace hierarchy

### Classes

Class | Description
--- | ---
Fastpath |
FastpathArg |
LargeObject |
LargeObjectManager | Summary description for LargeObjectManager.

### Structures

Structure | Description
--- | ---
NpgsqlBox |
NpgsqlCircle | Represents a PostgreSQL Circle type.
NpgsqlDate |
NpgsqlInet | Represents a PostgreSQL inet type.
NpgsqlInterval | Represents the PostgreSQL interval datatype. PostgreSQL differs from .NET in how it's interval type doesn't assume 24 hours in a day (to deal with 23- and 25-hour days caused by daylight savings adjustments) and has a concept of months that doesn't exist in .NET's TimeSpan class. (Neither datatype has any concessions for leap-seconds). For most uses just casting to and from TimeSpan will work correctly — in particular, the results of subtracting one DateTime or the PostgreSQL date, time and timestamp types from another should be the same whether you do so in .NET or PostgreSQL — but if the handling of days and months in PostgreSQL is important to your application then you should use this class instead of TimeSpan. If you don't know whether these differences are important to your application, they probably arent! Just use TimeSpan and do not use this class directly ? To avoid forcing unnecessary provider-specific concerns on users who need not be concerned with them a call to GetValue on a field containing an NpgsqlInterval value will return a TimeSpan rather than an NpgsqlInterval. If you need the extra functionality of NpgsqlInterval then use GetInterval.
NpgsqlLSeg | Represents a PostgreSQL Line Segment type.
NpgsqlPath | Represents a PostgreSQL Path type.
NpgsqlPoint | Represents a PostgreSQL Point type
NpgsqlPolygon | Represents a PostgreSQL Polygon type.
NpgsqlTime |
NpgsqlTimeStamp |
NpgsqlTimeStampTZ |
NpgsqlTimeTZ |
NpgsqlTimeZone |

### Enumerations

Enumeration | Description
--- | ---
NpgsqlDbType |