The official book is a good place to start - have you reviewed that yet?
http://web2py.com/books/default/chapter/29/06/the-database-abstraction-layer#Dependencies
On Wednesday, December 21, 2016 at 11:13:17 PM UTC-5, Steve Lyle wrote:
>
> Hi guys.
> Newbie (of sorts) here.
> 20+ years in programmi
Thanks!
On Monday, February 2, 2015 at 3:06:05 PM UTC-6, Niphlod wrote:
>
> uhm. Technically having more than one instance of mssql running on the
> same ip is possible (multiple named instances) but it involves a totally
> different connection handshake.
> If you don't specify different port n
uhm. Technically having more than one instance of mssql running on the same
ip is possible (multiple named instances) but it involves a totally
different connection handshake.
If you don't specify different port numbers, you can still have them
"dynamic" but you have to resort to have SQL Serve
Thank you for the reply. I found that that problem was why it doesn't
accept IP Address instead of Named Instance and fixed the SQL Server
configuration to use static IP to connect SQL Server.
I can't connect to my servers SQL database via an IP Address
http://dba.stackexchange.com/questions/62
The problem is that since you did not specify a name for the .table files
you get default (nobody does). default is a hash of the db uri so if you
change it the .table files break. If this is just a change in the name but
the tables are already in the database, the you should enable a
fake_migr
Thank you... / will try & feedback ..
:)
On Thursday, November 14, 2013 5:14:12 AM UTC+7, Derek wrote:
>
> Possible...
>
> Microsoft OLE DB Provider for ODBC Drivers error '80004005'
> [Microsoft][ODBC Driver Manager]Data source name not found and no default
> driver specified.
> This usually
Regardless, it's the same message just a different driver manager. I'd say
one of the settings being passed just won't work for mssql express, i'd
guess 'pooling'.
On Wednesday, November 13, 2013 3:25:38 PM UTC-7, Niphlod wrote:
>
> @derek: except that he's using unixodbc ^_^
>
> Anyway, goo
@derek: except that he's using unixodbc ^_^
Anyway, googling "[unixODBC][Driver Manager]Data source name not found"
leads you to several hundreds blogposts on the matter.
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source co
Possible...
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC Driver Manager]Data source name not found and no default
driver specified.
This usually happens in one of the following scenarios:
- you referenced your connection incorrectly (e.g. spelled the DSN n
Hello Tim,
Thank you for sharing.
I've try as your advice but it still return error message as follow, I
think something wrong with my odbc setup somehow.
:)
db = DAL('mssql://UserName:Password@203.150.29.227\SQLExpress/myDatabase',
lazy_tables=True, pool_size=10)
RuntimeError: Failure to con
Here is a working example using server authentication on a server called
win2003, with a sqlserver instance name hcnsql07 and connecting to a
database called hcn using default ports
(I've added a couple of other parameters for performance.
Investigate lazy_tables, it makes a huge difference. )
Got it with FreeTDS. Thanks
On Thursday, July 18, 2013 5:26:33 PM UTC-7, Niphlod wrote:
>
> plenty of references around the web it's a PITA to connect to MSSQL
> from a linux "client" but take advices even related to other programming
> languages to fix the odbc driver "bugs" and "intric
the best answer to that threat is freetds which I actually have had success
from Linux but is it supported by web2py?
On Thursday, July 18, 2013 5:26:33 PM UTC-7, Niphlod wrote:
>
> plenty of references around the web it's a PITA to connect to MSSQL
> from a linux "client" but take advices
will try. Thanks!!!
On Thursday, July 18, 2013 3:30:09 PM UTC-7, Marcio Andrey Oliveira wrote:
>
> Hi.
>
> I have no experience with web2py but it seems it's not able to read some
> file.
>
> Try to use strace command to determine what file is missing then you can
> search on the net which pa
plenty of references around the web it's a PITA to connect to MSSQL
from a linux "client" but take advices even related to other programming
languages to fix the odbc driver "bugs" and "intricacies", like
http://stackoverflow.com/questions/10728290/mssql-servers-native-odbc-driver-for-linux-
Hi.
I have no experience with web2py but it seems it's not able to read some
file.
Try to use strace command to determine what file is missing then you can
search on the net which package contains the missing file.
You can try something like
strace -o output.txt
or
strace -p -o output.t
Glad you were able to figure it out.
I solved the problem with HomeBrew
brew install unixodbc
brew install freetds
after that you can set up your dsn in Utilities iODBC.
Thank you.
--
Bruno Rocha
[ About me: http://zerp.ly/rochacbruno ]
On Thu, Mar 31, 2011 at 10:39 AM, Ross Peoples wrote:
> Bruno,
>
> I too have had this pro
Bruno,
I too have had this problem. It seems as if Mac OS X has some real problems
connecting to MSSQL, which isn't too much of a surprise I guess. The way
that I develop on Mac OS X may be crazy or over-complicated, but I find it
works well for me:
I set up a Ubuntu Server virtual machine in
Hi Bruno,
I had the same problem using MySQLdb, I solved it by setting up a
my.cnf file in /etc the following way:
Log in to OS X using an administrator-level account, open Terminal;
cd /usr/local/mysql/support-files/
sudo cp my-huge.cnf /etc/my.cnf
and enter your admin password when prompted.
It seens someone are having same issue woth Pyodbc and sqlalchemy
http://stackoverflow.com/questions/4665078/connect-to-mssql-from-sqlalchemy-by-pyodbc-on-mac-os
So it is not web2py DAL issue, it is Pyodbc issue, anyone aware?
On Tue, Mar 29, 2011 at 12:28 PM, Bruno Rocha wrote:
> HI,
>
> I am
21 matches
Mail list logo
