Malcolm Tredinnick wrote:
> On Wed, 2006-07-19 at 21:25 -0400, Joe wrote:
> I could have sworn I answered this just yesterday on this list:
> http://groups.google.com/group/django-users/browse_frm/thread/a13b9b12488569ef/549fa8112c0c97a7#549fa8112c0c97a7
>
> Short answer: "no problems".
Sorry, Ma
Joe,
On Thu, 2006-07-20 at 11:41 +1000, Malcolm Tredinnick wrote:
> On Wed, 2006-07-19 at 21:25 -0400, Joe wrote:
[...]
> > The database uses the CHAR(n) (or CHARACTER(n)) datatype in several
> > places, i.e., a fixed length character type, typically for very short
> > "code" type columns. inspe
On Wed, 2006-07-19 at 21:25 -0400, Joe wrote:
> Hi,
>
> I ran manage.py inspectdb on an existing PostgreSQL database and have
> some questions on the results.
>
> Three of the tables use the tsearch2 module which defines a 'tsvector'
> data type (to create a searchable text index). Currently, t
Hi,
I ran manage.py inspectdb on an existing PostgreSQL database and have
some questions on the results.
Three of the tables use the tsearch2 module which defines a 'tsvector'
data type (to create a searchable text index). Currently, the PHP app
is unaware of the existence of these columns, exc
4 matches
Mail list logo