Commit Graph

305 Commits

Author SHA1 Message Date
kevlo
095782cfb6 +p5-SQL-Statement 2001-05-20 13:06:44 +00:00
kevlo
5c7be622d3 Initail import of p5-SQL-Statement version 0.1020.
p5-SQL-Statement is a perl5 module for SQL parsing and processing.
2001-05-20 13:06:07 +00:00
shell
7e2c66f066 Upgrade to 0.85 2001-05-14 05:33:53 +00:00
shell
5c3104fd98 SUBDIR += p5-DBIx-XHTML_Table 2001-05-12 05:46:53 +00:00
shell
2a7d4a91d7 Initial import of p5-DBIx-XHTML_Table-0.83
---
This module was created to fill a need for a quick and easy way to
create 'on the fly' XHTML tables from SQL queries for the purpose
of 'quick and dirty' reporting.
2001-05-12 05:45:18 +00:00
naddy
7670a4e329 Use MACHINE_ARCH instead of ARCH in PLIST for m68k-based architectures.
Bump NEED_VERSION accordingly.
2001-05-10 19:20:40 +00:00
shell
4013156cbf - Change ARCH to MACHINE_ARCH
- bump VERSION
2001-05-08 11:23:59 +00:00
matt
c5c0cbe0bd - reorg existing JDKs, update devel/jdk dependencies
- become MAINTAINER for jdk 1.1 and 1.2 (ok MAINTAINERs)
- add jdk 1.3
2001-05-08 00:54:36 +00:00
wilfried
d926010079 Use MACHINE_ARCH instead of ARCH && bump NEED_VERSION 2001-05-07 11:51:03 +00:00
lebel
72be062198 databases: beuhbye COMMENT, bump NEED_VERSION 2001-05-05 23:24:50 +00:00
espie
b186afd8b2 , -> : in flavor deps. 2001-05-05 21:28:04 +00:00
espie
594099de65 Patches to fix dynamic libraries, especially on ppc which understands
only major/minor.

Add DYNLIBDIR where needed.

Some style issues.

From peter@, brad@ and peter_e@gmx.net
2001-04-23 21:58:44 +00:00
peter
8e947ac808 take over as maintainer, agreed with kevlo@
integrate COMMENT
bump NEED_VERSION
change postgresql settings for updated package

reformat and slightly reword DESCR

ok espie@
2001-04-23 12:38:17 +00:00
lebel
f376f701f5 PERMIT_PACKAGE_*: Yes to No, since there is no clear license. 2001-04-22 14:01:34 +00:00
peter
9c67d66ac2 add '-m fast' to rc.shutdown suggestion, as otherwise the shutdown process
will default to waiting for all clients to disconnect - which could be never
2001-04-22 09:35:00 +00:00
peter
f436f5f836 oops. Thanks Peter Valchev for noticing. 2001-04-21 22:28:47 +00:00
peter
f255c13dfa add FLAVOR="tcl odbc" postgresql build. ok espie@ 2001-04-21 19:12:55 +00:00
peter
e827943d23 Add FLAVOR="odbc" for postgresql port. ok espie@ 2001-04-21 19:05:45 +00:00
peter
fd69a6d25a Upgrade to postgresql 7.1. ok'd espie@
* The package is now called `postgresql' and not `pgsql'.

* The default user that is suggested for the admin account is also
  `postgresql'. This will work with OpenBSD-current with long username
  support. If anything breaks please report to the maintainers.

* pgwrap is no longer shipped or supported

* Please note, you will HAVE TO BACKUP your old data if you are
  upgrading from a previous release of postgresql. Do this before
  removing the old pgsql package.

From the announcement last weekend:

Key New Features and Capabilities of Version 7.1 Include:

* Write-ahead Log (WAL) increases data integrity and processing
speed. To maintain database consistency in case of an operating
system crash, previous releases of PostgreSQL have forced all all
data modifications to disk before each transaction commit. With
WAL, only one log file must be flushed to disk, greatly improving
performance. (Tech note: can eliminate use of -F in to disable disk
flushes)

* TOAST (The Oversized-Attribute Storage Technique) Past releases
had compiled-in row length limit typically between 8Kb & 32Kb. This
restriction made storage of long text fields difficult, cumbersome
and slow. TOAST enables rows of any length while maintaing the high
performance PostgreSQL users have come to expect.

* SQL92 Outer Joins are now supported. (Tech note: eliminates the
UNION/NOT IN workaround)

* 64-bit C Language Function Manager support The previous C function
manager did not handle support 64-bit CPU's (e.g. Alpha, Sun,
Itanium). (Tech note: This change should not impact existing custom
functions developed for past versions, but performance will be
improved through rewriting to use the new call interface.)

* Complex Queries that are better, stronger and faster Many complex
queries were unsupported in previous releases. With v7.1 combinations
of views, aggregates, UNION, LIMIT, cursors, subqueries, and inherited
tables are enabled. Inherited tables are now accessed by default,
and subqueries in FROM are now supported.
2001-04-21 18:25:42 +00:00
jakob
9e550b807f fix sasl flavour; <op21@squish.org> 2001-04-20 23:10:43 +00:00
avsm
1969ce17c9 update the checksum for mysql-3.23.37 too 2001-04-20 15:43:44 +00:00
brad
f1f7315d48 upgrade to MySQL 3.23.37 2001-04-20 13:49:38 +00:00
wilfried
c6a80a4078 Upgrade to 1.7.5
From doc/readme.version_1.7.5:

Regarding bug fixes, foremost of all, some of FLTK widgets have
been updated, which has caused some changes in mysqlgui source code.
Some users have reported problems with X 4.0.* when using some
widgets. This has been fixed. Beside that, column resizing in
spreadsheet now works. Also, editing (in order to scroll text) and
zooming is not automatic, but you should press F2 or Ctrl+E in order
to scroll a cell or to zoom it. This has resulted in faster scrolling
of the spreadsheet. Some aesthetic changes have been implemented
in some widgets. Also, process dialogue display is now more readable.
2001-04-20 09:40:52 +00:00
espie
a4b09c3092 no longer conflicts with xemacs-sumo. 2001-04-18 23:34:15 +00:00
shell
b2e65e7ad1 Add the missing WWW: ${HOMEPAGE},
ok avsm@
2001-04-18 18:23:35 +00:00
shell
1c0bc3c150 SUBDIR += py-mysql 2001-04-18 17:53:34 +00:00
shell
9aa8a51184 Import py-mysql-0.3.5
Python interface to MySQL-3.22 and 3.23

MySQLdb is an interface to the popular MySQL database server for
Python.  The design goals are:

-     Compliance with Python database API version 2.0
-     Thread-safety
-     Thread-friendliness (threads will not block each other)
-     Compatibility with MySQL 3.22 and 3.23
2001-04-18 17:47:05 +00:00
ian
46ed52d695 Typo in cygnus URL in MASTER_SITES (ok maintainer) 2001-04-18 16:33:09 +00:00
shell
b0165f9059 Change MAINTAINER email address 2001-04-17 06:26:52 +00:00
espie
ebb4a3c69d conflict 2001-04-15 17:30:32 +00:00
espie
8f5a931245 Broken conflicts 2001-04-15 16:48:44 +00:00
wilfried
0fc8667bad change fltk and fleditor dependings 2001-04-15 10:33:09 +00:00
lebel
5d9d71f72e delete rogue COMMENT file. asked by shell@ 2001-04-14 13:26:11 +00:00
brad
2b84c015aa add innodb FLAVOR to build MySQL with transaction support using InnoDB
(currently known throughout as Innobase though it will be renamed as of
MySQL 3.23.37 and up).
2001-04-13 18:15:46 +00:00
brad
cc6ce411e4 - integrate COMMENT's
- bump NEED_VERSION
- use PKGNAME-foo instead of overriding PKGNAME
- fixup INSTALL/DEINSTALL
- takeover as MAINTAINER until Pavel has a working e-mail address that
doesn't bounce.
2001-04-13 07:00:44 +00:00
brad
e8c5824fd0 roll back NEED_VERSION by one revision. 2001-04-10 16:12:48 +00:00
lebel
0fc33abcc9 integrate COMMENT into Makefile. Change my email. naddy@ OK. 2001-04-10 13:33:14 +00:00
espie
6d8f038330 Bye, bye COMMENT 2001-04-10 00:57:27 +00:00
brad
7c3a0e7a56 same for Innobase and Gemini database(s). 2001-04-07 04:09:53 +00:00
brad
3970eb3500 ensure MySQL doesn't try to enable Berkeley DB transaction support by
default if it happens to be installed.
2001-04-07 03:26:49 +00:00
brad
3f74c4e167 Use , for FLAVORs. 2001-04-05 03:46:25 +00:00
danh
26f45d9d22 - update checksum.
- change version to date.
- add RUN_DEPENDS on databases/p5-DBI.
2001-04-04 13:59:46 +00:00
wilfried
e3df7c662d A bit of my development path was left, thanks jakob@ 2001-04-03 06:57:18 +00:00
avsm
a6d4f163cf Update to p5-DBI-1.15, from maintainer 2001-04-02 15:57:11 +00:00
wilfried
2e7833a35f add mysqlgui 2001-04-02 15:17:42 +00:00
wilfried
d3e39d11da Import of mysqlgui-1.7.4
graphical sql client for MySQL
2001-04-02 15:14:51 +00:00
danh
8f943e3317 add homepage 2001-03-30 21:11:01 +00:00
danh
2649f55e19 +mysql2pgsql 2001-03-30 21:09:31 +00:00
danh
ab06f4cc09 Import of mysql2pgsql 1.8
from DESCR:
The perl script mysql2pgsql can be used to convert MySQL database
dumps to a PostgreSQL-compatible format (so the data can be imported
into PostgreSQL).  This can be useful if you are switching from
MySQL to PostgreSQL and you have quite a bit of data in your MySQL
databases.

Submitted by:	Pete Fritchman <petef@databits.net>
2001-03-30 21:08:25 +00:00
brad
4e2d38df35 upgrade to MySQL 3.23.36 2001-03-28 22:12:18 +00:00