Skip to content
Snippets Groups Projects
Select Git revision
  • chacha96
  • master default
  • support_pre_UAL_arm_asm
  • skein
  • rsa-crt-hardening
  • fat-library
  • versioned-symbols
  • curve25519
  • dsa-reorg
  • aead-api
  • set_key-changes
  • poly1305
  • aes-reorg
  • nettle-2.7-fixes
  • size_t-changes
  • ecc-support
  • experimental-20050201
  • lsh-1.4.2
  • nettle_3.3_release_20161001
  • nettle_3.2_release_20160128
  • nettle_3.1.1_release_20150424
  • nettle_3.1_release_20150407
  • nettle_3.1rc3
  • nettle_3.1rc2
  • nettle_3.1rc1
  • nettle_3.0_release_20140607
  • nettle_2.7.1_release_20130528
  • nettle_2.7_release_20130424
  • nettle_2.6_release_20130116
  • nettle_2.5_release_20120707
  • converted-master-branch-to-git
  • nettle_2.4_release_20110903
  • nettle_2.3_release_20110902
  • nettle_2.2_release_20110711
  • nettle_2.1_release_20100725
  • camellia_32bit_20100720
  • nettle_2.0_release_20090608
  • nettle_1.15_release_20061128
38 results

chacha-poly1305.c

Blame
  • Forked from Nettle / nettle
    Source project has a limited visibility.
    postgres.pike 13.72 KiB
    /*
     * This is part of the Postgres module for Pike.
     *
     * $Id: postgres.pike,v 1.32 2008/07/05 11:17:45 srb Exp $
     *
     */
    
    //! This is an interface to the Postgres (Postgres95, pgsql) database
    //! server. This module may or may not be availible on your Pike,
    //! depending whether the appropriate include and library files could
    //! be found at compile-time. Note that you @b{do not@} need to have a
    //! Postgres server running on your host to use this module: you can
    //! connect to the database over a TCP/IP socket.
    //!
    //! @note
    //! Also note that @b{this module uses blocking I/O@} I/O to connect
    //! to the server. Postgres is quite slow, and so you might want to
    //! consider this particular aspect. It is (at least should be)
    //! thread-safe, and so it can be used in a multithread environment.
    //!
    //! The behavior of the Postgres C API also depends on certain
    //! environment variables defined in the environment of the Pike
    //! interpreter.
    //!
    //! @string
    //!   @value "PGHOST"
    //!     Sets the name of the default host to connect to. It defaults
    //! 	to @expr{"localhost"@}.
    //!   @value "PGOPTIONS"
    //!     Sets some extra flags for the frontend-backend connection.
    //!     @b{do not set@} unless you're sure of what you're doing.
    //!   @value "PGPORT"
    //!     Sets the default port to connect to, otherwise it will use
    //!     compile-time defaults (that is: the time you compiled the postgres
    //! 	library, not the Pike driver).
    //!   @value "PGTTY"
    //!     Sets the file to be used for Postgres frontend debugging.
    //!     Do not use, unless you're sure of what you're doing.
    //!   @value "PGDATABASE"
    //!     Sets the default database to connect to.
    //!   @value "PGREALM"
    //!     Sets the default realm for Kerberos authentication. I never used
    //!   	this, so I can't help you.
    //! @endstring
    //!
    //! Refer to the Postgres documentation for further details.
    //!
    //! @seealso
    //!  @[Sql.Sql], @[Postgres.postgres], @[Sql.postgres_result]
    
    #pike __REAL_VERSION__
    
    #if constant(Postgres.postgres)
    
    #define ERROR(X) throw (({X,backtrace()}))
    
    inherit Postgres.postgres: mo;
    private protected mixed  callout;
    private string has_relexpires = "unknown";
    
    //! @decl void select_db(string dbname)
    //!
    //! This function allows you to connect to a database. Due to
    //! restrictions of the Postgres frontend-backend protocol, you always
    //! have to be connected to a database, so in fact this function just
    //! allows you to connect to a different database on the same server.
    //!
    //! @note
    //! This function @b{can@} raise exceptions if something goes wrong
    //! (backend process not running, not enough permissions..)